mdma_query

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

With no annotations, the description carries the full burden, yet it discloses nothing about safety, permissions, or return behavior. Worse, framing the tool as 'Inspect' conceals that 'delete_all_requests' is a destructive bulk operation — the single most important behavioral fact about this 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?

One tight sentence with no filler, and the resource is front-loaded after the verb. It is efficiently written; the problem is omission, not verbosity.

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?

Six actions, one of them a destructive bulk delete, no annotations, and no output schema — the description should flag the destructive action and the target/index addressing rules. As written an agent could select delete_all_requests believing this is a pure read tool.

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 coverage is 100%, so all four parameters, including the action enum and its per-action index/target semantics, are already documented. The description adds only a vague hint that requests and channels are addressable, which is baseline-level value.

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 ('Inspect') and resource (MDMA requests and channels), plus useful family context (H7/U5/N6). It does not name the sibling that performs writes (mdma_mutate), and 'Inspect' understates the scope given the action enum includes delete_all_requests.

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 statement of when to call this versus mdma_mutate or dma_query, and no prerequisites. The agent must infer from the word 'Inspect' that this is the read path, which is contradicted by one of the available actions.

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