explain

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

The description lacks behavioral details such as whether the tool is read-only, requires special permissions, or has side effects. The term 'trace' hints at analysis, but no explicit safety or mutation information is given. With no annotations, the description fails to provide necessary transparency.

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 a single, concise sentence, but it is under-specified. While brevity is good, it sacrifices clarity and completeness on crucial details.

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?

Without an output schema or annotations, and with low schema coverage, the description is severely incomplete. It does not explain what an 'EXPLAIN trace' returns, how to use parameters, or any contextual prerequisites for the agent.

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 low (20%) with only token described. The description adds minimal parameter meaning: it hints that 'kind' relates to query kinds and mentions args, but does not explain other parameters like depth, start, or value. This does not compensate for the schema gaps.

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 identifies the tool as performing an 'EXPLAIN trace' for a query, mentioning 'kind + its args, as query_*'. This clearly states the verb and resource, and the mention of 'query_*' suggests a specific scope that differentiates from sibling tools like query_by_id or query_by_kind.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling tools include various query retrieval and search tools, but the description does not specify contexts where explain is appropriate or when other tools should be used instead.

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