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

No annotations are provided, so the description carries the burden of behavioral disclosure. It discloses that the tool returns an integrity score and severity-ranked flags, and mentions the cost model. It does not explicitly state whether the operation is read-only, but 'validation pass' strongly implies non-destructive behavior. However, it omits details on error handling, required financial data structure, or rate limits beyond pricing, leaving some gaps.

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 compact, using a colon-separated list to enumerate validation checks in the first sentence and a second sentence for output and pricing. It is efficiently structured with no wasted words, though the dense list could be slightly harder to parse quickly. The pricing note is extra but useful.

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 (nested object parameter, no output schema, no annotations), the description is incomplete. It explains the output (integrity score + flags) and lists the checks, but it does not describe the input structure, nor does it provide guidance on when to use this tool versus siblings like sec_extract or deal_score. This leaves significant gaps for an agent to correctly invoke the tool.

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?

The schema has a single 'financials' object parameter with no description and 0% schema description coverage. The tool description does not explain the structure or required fields within the financials object, leaving the agent without guidance on how to construct valid input. This is a critical gap.

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 an 'institutional validation pass' over company financials, specifying concrete validation checks like tax-rate sanity, EBITDA/EBIT bridge, and growth continuity. This specific verb+resource structure distinguishes it from sibling tools like company_report (report generation), deal_score (scoring deals), and sec_extract (extracting SEC data).

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 implies the tool is used for validating financial integrity, but it does not explicitly state when to use it over the sibling tools or provide exclusions. It lacks direct comparative guidance, so the usage context is implied rather than explicit.

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