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

The description adds substantial behavioral context beyond the annotations: it details the exact data pulled for each type (SEC XBRL financials for companies, FAERS counts for drugs), notes correct handling of off-calendar fiscal years, explains sorting by primary metric, and mentions return of citation URIs. This fully informs the agent of the tool's behavior.

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 moderately concise, using bolded trigger phrases and a clear structure. While it packs a lot of information, a few sentences could be slightly tightened without losing meaning.

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 has no output schema, the description partially explains return values ('paired data + pipeworx:// citation URIs') but is somewhat vague on the exact structure. However, for a tool with only 2 parameters and clear purpose, it is largely complete.

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 meaningful context: it explains the data sources for the 'type' parameter and provides examples for 'values' (tickers/CIKs for companies, drug names). It also clarifies constraints (2-5 items) and data retrieval specifics.

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 comparisons of entities, specifies trigger phrases ('X vs Y', 'which is bigger', etc.), and distinguishes between company and drug data sources. It effectively communicates the tool's unique value over sibling tools like 'entity_profile'.

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 says 'ALWAYS PREFER over sequential single-pack lookups' and claims to replace 8-15 sequential lookups, providing strong usage guidance. However, it does not explicitly mention when not to use it (e.g., for single entity lookups) nor directly name sibling tools as alternatives.

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