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

The description explicitly says 'Does not execute changes,' which is valuable behavioral context, especially because readOnlyHint is false. It also clarifies that the tool returns packets rather than applying fixes. It does not elaborate on external calls, but openWorldHint already encodes that.

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 three short sentences with no filler. It front-loads the core action, then the output, then the critical non-execution behavior, so each sentence earns its place.

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 a tool with only two parameters, full schema coverage, and an output schema, the description is nearly complete. The only notable gap is explicit guidance on when to choose this tool over related siblings, which prevents a perfect score.

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?

With 100% schema description coverage, the baseline is 3, but the description adds meaningful context by limiting `text` to API, EVM RPC, or webhook errors and by mentioning sanitization. The `source` parameter remains adequately explained by 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 states a specific verb-resource pair: sanitize and match API, EVM RPC, or webhook errors to FixGraph, and it defines the output as machine-readable repair packets. It also distinguishes the tool from siblings by clarifying that it does not execute changes, so an agent can tell it apart from retrieval or action-oriented tools.

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 when to use the tool: when the agent has a technical error and needs a matching repair packet. However, it does not explicitly route the agent away from sibling tools like get_repair_packet or list_fix_topics, and it does not state when not to use this tool.

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