Add a package to the caller’s own private watchlist, so later readings are about their stack rather than the public one. The list is private to the key that created it. Requires a key; see https://sighttrue.com/pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Package name as the registry spells it. | |
| registry | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses privacy ('list is private to the key that created it') and the auth requirement ('Requires a key'), but doesn't mention idempotency or behavior on duplicate additions. More behavioral detail would be helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise, front-loaded sentences. Each sentence adds value: purpose, privacy, and key requirement. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple add-to-list tool, the description covers the main purpose, privacy, and key requirement. However, it doesn't clarify behavior on duplicate entries, return values, or how 'registry' influences the action. Still, it's reasonably complete for basic selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: 'name' has a description, 'registry' does not. The description doesn't elaborate on either parameter and doesn't explain how they are used together. It adds little beyond the schema, especially for the undocumented 'registry' parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action: 'Add a package to the caller’s own private watchlist.' It specifies the resource (private watchlist) and distinguishes itself from siblings like watch_changes by emphasizing the private, caller-specific nature.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides context on when to use ('so later readings are about their stack rather than the public one') and a prerequisite ('Requires a key'). It doesn't explicitly mention alternatives or exclusions, but the usage context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct query type: package status, stack review, provider incidents, model pricing, watchlist changes, etc. Even similar-sounding tools like check_package and check_stack are clearly differentiated by granularity (single package vs. whole manifest). The descriptions further remove ambiguity.
All names use lowercase snake_case, but the pattern is mixed: some are imperative verb_noun (check_package, find_model, watch_add) while many are noun phrases (advisory_severity, provider_incidents, runtime_deadlines). This is readable but not a consistent verb_noun style, so there is noticeable inconsistency.
At 31 tools, the count exceeds the 'too many' threshold (25+). While the domain is broad, the agent must navigate a large surface with many similarly scoped utilities, making selection harder. A more consolidated set (e.g., grouping related readings) would improve appropriateness.
The tool surface covers a wide range of supply-chain intelligence: package advisories, provider status, model pricing, runtime EOL, and watchlist changes. The only notable gap is lifecycle management for the private watchlist (e.g., no watch_remove or watch_list), but the overall coverage is strong.