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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds that the test is 'bounded' and 'free' and mentions approving safe reads, but does not disclose what is destroyed, permission requirements, or how the required idempotency_key is used.

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 sentences, front-loaded with the purpose. The second sentence compactly lists workflow steps, though it could be broken out; no obvious filler.

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 complex 9-parameter destructive mutation tool with no output schema and 0% schema description coverage, the description is too thin. It omits prerequisites, parameter details, return behavior, and consequences of starting the trial.

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% across 9 parameters, so the description must carry parameter meaning. It hints at upstream_url ('public HTTPS MCP server') and safe_read_tools ('safe reads'), but leaves required name, policy_version, accept_terms, idempotency_key, cache_ttl_seconds, min_shadow_matches, and tool_costs_microusd semantically unexplained.

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?

Starts with a specific verb and resource: 'Start a bounded free gateway test', and outlines the workflow (connect server, approve safe reads, verify repetition). It does not differentiate from sibling tools mithrandir_demo or mithrandir_security_profile.

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 explicit when-to-use or when-not-to-use guidance is provided. The second sentence describes an internal sequence, not conditions for choosing this tool over the sibling tools.

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