watchlist_new_targets

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden but supplies none: no statement that it is a read-only query, no auth/scope requirements, no pagination or result-size behavior, and no explanation of what 'in-scope' means or how 'since' bounds results.

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?

A single front-loaded sentence with no filler, so it is appropriately sized given the intent. It is arguably too terse, but nothing in it is wasted.

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 tool with no annotations, no output schema, and half the parameters undocumented, the description is too thin. It should at least clarify what a 'target' is, what counts as 'new', and the shape of the return.

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%, and program_ids has an empty schema description. The description's 'list of programs' and 'since a timestamp' partially map to both params, but add little beyond the schema's own 'ISO timestamp; default 7 days ago' text and don't explain format or filtering semantics for program_ids.

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 verb phrase 'new in-scope targets ... since a timestamp' conveys what is returned, but it doesn't clarify the 'watchlist' concept from the name or distinguish it from siblings like recent_target_changes, list_targets, and search_targets, which all touch targets.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance is given. An agent cannot tell from the description whether to reach for this versus recent_target_changes or list_targets for a similar need.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.