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

The description goes well beyond the annotations (readOnlyHint, openWorldHint, idempotentHint) by detailing data sources (SEC EDGAR/XBRL, FAERS), handling of off-calendar fiscal years, sorting by primary metric, inclusion of pipeworx:// citation URIs, and estimated reduction of 8–15 sequential lookups. No contradictions 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 dense but every sentence provides value. It is front-loaded with the core purpose and usage triggers, followed by data-source details and return format. No fluff or repetition—each clause adds necessary information for correct tool invocation.

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 complexity (two entity types, multiple data sources, sorting, citations) and the lack of an output schema, the description is exceptionally complete. It covers what data is pulled, how results are ordered, what return artifacts to expect, and when to prefer this tool. No critical operational detail is left unspecified.

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?

Although the schema already covers 100% of parameter descriptions, the description enhances meaning by explaining how 'type' determines the data source and output (company vs drug) and providing concrete examples for 'values' (e.g., ["AAPL","MSFT"], ["ozempic","mounjaro"]). It also clarifies size constraints and sorting behavior, adding context beyond the raw schema.

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 performs side-by-side comparisons of 2–5 companies or drugs in one parallel call, with specific verbs like 'compare', 'rank', and 'head to head'. It distinguishes itself from sequential lookups and sibling tools like entity_profile by explicitly positioning itself as the preferred alternative for comparison tasks.

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 provides explicit usage triggers ('Compare X and Y', 'X vs Y', 'which is bigger / better / larger / more profitable', etc.) and a strong directive ('ALWAYS PREFER over sequential single-pack lookups when comparing entities'). It also implies the alternative (sequential lookups) and clarifies when to use this tool versus those.

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