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

Annotations already provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds context: it covers deals with a US-listed party due to SEC filings, and explicitly states it answers open-ended questions. No contradiction with annotations.

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 a single paragraph that front-loads the purpose and return fields, then adds example queries and the source. It's slightly long but every sentence contributes to scope or usage. No redundancy.

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 read-only search tool with 100% schema coverage, the description covers purpose, outputs, source, limitations, and filtering options. Since there is no output schema, it describes the return fields. Minor gaps: sorting order and pagination behavior beyond a limit parameter are not mentioned, but these are not critical.

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 100%, so all parameters are documented with types and defaults. The description adds marginal value by explaining that 'query' narrows the search and is combined with (not replacing) the deal/China terms, and that 'since' defaults to 90 days ago. This aligns with the schema but doesn't go much beyond it.

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 uses a specific verb ('Returns'), names the exact resource (China licensing deals), and enumerates the fields returned: companies, drug/asset, territory, upfront payment, milestone totals, royalty terms, SEC filing and date. It clearly distinguishes itself from siblings by its subject matter and scope.

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 explicitly lists example queries it answers ('which Chinese biotechs signed out-licensing deals', 'recent China pharma licensing deals', 'who licensed rights in Greater China') and explains the data source (SEC 8-K) plus its coverage limitation (deals with a US-listed party). It implies when to use this tool over alternatives (for China licensing deals), though it does not name sibling tools explicitly.

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