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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds rich behavioral details: data sources (SEC EDGAR/XBRL, FAERS), handling of off-calendar fiscal years, sorting by primary metric, return of paired data plus citation URIs, and efficiency benefit (replaces 8–15 lookups). These go well beyond the 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 well-organized, starting with trigger phrases, then core function, data details, output behavior, and efficiency. Every sentence adds value, though it is somewhat long; a slight trim would make it more concise without losing information.

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?

With no output schema, the description adequately covers return values (paired data + pipeworx:// URIs), input semantics, data sources, sorting, and edge cases (off-calendar fiscal years). For a tool with only two parameters and moderate complexity, it is complete enough for an agent to select and invoke correctly.

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, but the description adds significant meaning: it explains what each 'type' value pulls (10-K metrics for company, adverse-event/trial counts for drug) and provides examples for 'values'. This enriches the schema definitions meaningfully, though it doesn't add format details beyond the 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 trigger phrases like 'Compare X and Y' and 'rank these companies'. It distinguishes itself from sequential single-pack lookups, making it unique among siblings such as 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?

Explicitly provides when-to-use examples ('X vs Y', 'which is bigger', 'head to head') and states 'ALWAYS PREFER over sequential single-pack lookups when comparing entities', which is a clear alternative/exclusion. It also differentiates between company and drug types, giving context for each.

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