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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context: 'pulls LATEST 10-K revenue...', 'off-calendar fiscal years handled correctly', returns 'pipeworx:// citation URIs per entity', and 'results sorted by primary metric'. This goes beyond annotations, though rate limits or caching are not mentioned.

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 dense block but packs essential information efficiently. Every sentence adds value—usage examples, data sources, ordering, and substitution benefit. It could be slightly more structured (e.g., bullet points), but overall it is concise and well-organized.

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 tool's moderate complexity (2 params, no output schema), the description covers key aspects: what it does, when to use, what data each type returns, and the substitution value. Missing details like error handling for invalid inputs or rate limits, but these are not critical. It places the tool in context of sibling tools by noting it replaces 8–15 sequential lookups.

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 baseline is 3. The description adds meaning: for type='company' it specifies data sources (SEC EDGAR/XBRL) and specific financial fields; for type='drug' it lists FAERS counts, FDA approvals, trial counts. It also clarifies the array items (tickers/CIKs for company, names for drug) and the maxItems=5 constraint.

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 it performs side-by-side comparison of 2–5 companies or drugs in one parallel call. It uses specific verbs and resources ('compare', 'side-by-side comparison', 'companies or drugs') and distinguishes from sibling tools like entity_profile by emphasizing it replaces sequential lookups.

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?

Explicit when-to-use guidance is given: phrases like 'compare X and Y', 'X vs Y', 'which is bigger', 'rank these companies', 'head to head'. It also states 'ALWAYS PREFER over sequential single-pack lookups when comparing entities', providing a clear preference directive and context for avoiding alternatives.

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