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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true — a rich set. The description adds only the pricing ($0.10 USDC per call), which IS useful behavioral context (cost before invocation). But it discloses nothing about what the 'summary' contains, output shape, latency, or the open-world/network behavior. Pricing alone is thin against a multi-step analysis tool.

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?

A single em-dash-delimited clause that front-loads the bundle scope, enumerates the three operations, and appends pricing. No wasted words.

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?

No output schema exists, so the description needs to convey what comes back — it says 'classification + field extraction + summary' but never describes the return format or field structure. For a composite analysis tool that costs money per call, the agent lacks enough to know what it will receive.

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 description coverage is 0%, but there is only one parameter: 'text'. The description implies the text is the insurance document/content to analyze but never says so explicitly. With a single required param and zero schema coverage, the description should have clarified what 'text' should contain — a minor gap given only one parameter.

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?

States a specific verb+resource ('Full insurance analysis bundle') and enumerates the three sub-operations (classification + field extraction + summary). It's distinguishable from siblings like classify-insurance or extract, which appear to be the decomposed versions of this bundle. Score 4 because it doesn't explicitly name those siblings as alternatives.

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 'bundle' framing implies a use case (get everything in one call), which is implied usage guidance. But it doesn't state when to prefer this over calling classify-insurance, extract, and summarize separately, nor when it's inappropriate. No explicit when/when-not.

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