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

Annotations declare readOnlyHint, idempotentHint, non-destructive, and non-open-world. The description adds that the tool 'validates its structure' and accepts 'analysis results, never model bytes', which is useful behavioral context. However, it doesn't explain what happens upon validation failure, retry behavior, or the output beyond what the output schema covers.

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?

Two concise sentences, front-loaded with the core action. No wasted words. Could be slightly more informative but is efficient.

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 complex nested input, rich annotations, and presence of an output schema, the description covers the basic scope and clarifies it's not for model bytes. However, it doesn't address common failure modes, validation expectations, or how the result is used downstream. The parameter semantics gap is the main shortfall.

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%, so the description carries the full burden for the single complex 'result' parameter with many nested required fields. The description only states it accepts 'one bounded browser-produced DEEPBOM result' and 'never model bytes', which gives some scope but doesn't explain the required schema fields or the implications of the nested structure. This leaves significant ambiguity for an agent constructing the argument.

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: 'receives', 'validates', 'returns' a 'DEEPBOM analysis result' to the conversation. This is clear enough to distinguish from deepbom_publish_error (publishes errors rather than analysis results) and deepbom_analyze_file (produces analysis rather than returns it). It could more explicitly name the sibling it's not.

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 usage ('browser-produced DEEPBOM result', 'returns it to the conversation') but does not state when to use this tool versus alternatives or when not to use it. There's no explicit routing guidance for the agent.

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