watchlist_brief

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

No annotations are provided, so the description carries full burden. It describes output format and sorting, but does not disclose side effects, permissions, or whether the tool is read-only. The read-only nature is inferred but not explicit.

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?

The description is two concise sentences, front-loaded with the main purpose, and no unnecessary words. It efficiently communicates the tool's output and sorting.

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?

Given the simple tool (one parameter), the description provides adequate context about output content. However, it omits necessary preconditions like the watchlist must exist, and does not mention error handling or edge cases.

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?

The schema has one parameter 'watchlist_id' with 0% description coverage. The description does not mention the parameter or explain how to obtain the watchlist ID, missing an opportunity to clarify parameter meaning.

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 clearly states the tool's purpose: 'Generate a scored intelligence brief for every symbol on a watchlist.' It specifies the output fields (active signal count, catalyst flag, etc.) and sorting, distinguishing it from siblings like 'get_watchlist' which likely returns raw watchlist data.

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?

The description implies the tool is used to get scored intel on a watchlist, but does not explicitly state when to use it over alternatives like 'get_watchlist' or other analytical tools. No 'when not to use' or alternative suggestions are provided.

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