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

The description adds substantial behavioral context beyond the readOnlyHint annotations, including data sources (SEC EDGAR/XBRL, FAERS), handling of off-calendar fiscal years, sorting by primary metric, and return of paired data plus pipeworx:// citation URIs. 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 concise yet dense, packing trigger phrases, usage rules, data-source details, sorting behavior, and return format into a structured paragraph. Every sentence serves a purpose, and the critical 'ALWAYS PREFER' guidance is front-loaded.

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?

Despite having no output schema, the description fully explains what the tool returns (paired data + citation URIs), covers both entity types, mentions edge cases (off-calendar fiscal years), and clarifies the sort order. It is complete for a tool with this complexity and parameter scope.

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 already provides 100% coverage of both parameters, so the baseline for value-add is 3. The description further enriches meaning by explaining what data each type pulls (company: 10-K revenue, net income, cash, long-term debt; drug: adverse-event counts, FDA approvals, trials) and clarifies the values array semantics with examples, justifying a 4.

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 explicitly states the tool performs side-by-side comparison of 2–5 companies or drugs in a single parallel call, with specific trigger phrases ('X vs Y', 'which is bigger'). It distinguishes itself from sequential single-pack lookups, which are the clear alternative.

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 gives a direct usage directive: 'ALWAYS PREFER over sequential single-pack lookups when comparing entities,' and specifies the contexts for company vs. drug types. It clearly tells the agent when to choose this tool over alternative approaches, though it does not name specific sibling tools.

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