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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds the return shape ('claims grouped by section, industry, confidence, and evidence type'), which matters because there is no output schema, but it says nothing about pagination behavior or result-set size despite page/limit parameters.

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?

Three short sentences with the core capability front-loaded and no repetition. The final comparative sentence is slightly informal ('More powerful') but it earns its place by routing the agent away from a sibling.

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?

For an 8-parameter, zero-required search tool with no output schema, the description conveys what comes back at a grouping level but omits pagination semantics and what an unfiltered/queryless call returns. It is adequate but leaves real gaps for a tool this configurable.

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 100%, so every one of the 8 parameters is already documented in the schema and the baseline is 3. The description mentions the faceting axes (section, industry, confidence, evidence) that correspond to four filters but adds no syntax, default, or semantics beyond what the schema provides.

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 and resource ('deep search across the OTP intelligence base') plus the defining capability (faceted filtering) and the return grouping. It explicitly names the sibling it supersedes ('More powerful than search_claims'), so an agent can distinguish it without opening either schema.

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 comparison to search_claims implies the routing rule (use this when you need faceted/deep search), but it never states the condition explicitly nor says when search_claims or discover_intelligence is the better choice. Usage is inferable rather than directed.

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