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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. Description adds rich behavioral context: explains how off-calendar fiscal years are handled, data sources per type, results sorted by primary metric, and inclusion of citation URIs. 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?

Description is a single dense paragraph that front-loads key use cases with example queries. It efficiently packs purpose, data sources, behavior, and efficiency gains. Could be slightly more structured with bullet points, but it's concise and informative.

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 there is no output schema, the description adequately explains returns as 'paired data + pipeworx:// citation URIs per entity' and mentions sorting. It covers data sources, limitations (max 5 entities), and efficiency benefit. For a comparison tool, this is sufficient, though more detail on the exact fields returned would be helpful.

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 covers both parameters with descriptions (100% coverage). Description reinforces meaning with concrete examples: for type enum it specifies data sources, for values it mentions tickers/CIKs for companies and drug names. This adds context beyond the schema's basic descriptions.

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?

Description clearly states it performs side-by-side comparison of 2-5 companies or drugs, with specific data sources (SEC EDGAR/XBRL for companies, FAERS/FDA for drugs). Example queries like 'compare X and Y' and 'rank these companies' make the purpose immediately understandable. It distinguishes itself from siblings like entity_profile by noting it replaces 8-15 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?

Explicitly advises to prefer this tool over sequential single-pack lookups when comparing entities, with examples of natural language triggers. It implies when to use but doesn't explicitly state when not to use or list alternatives. However, the context of replacing many lookups is strong guidance.

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