system_debug_srr_matcher

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

With no annotations, the description carries the full behavioral burden but discloses only that the endpoint is a POST. It does not say whether this test has side effects, requires elevated auth, validates or persists the supplied rules, or what it returns.

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?

Three auto-generated lines that are terse but under-specified rather than concise; the purpose is not front-loaded and the tag line adds no information. Efficiency here reflects a generator stub, not deliberate structure.

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 a deeply nested body schema, no output schema, and no annotations, the description omits everything an agent needs: what the matcher evaluates, what a successful test produces, and whether the operation mutates state.

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 50% and the description adds zero parameter meaning — no explanation of the body, responseRules, or the confirm flag. While the nested schema is itself well documented, the description contributes nothing to compensate for the uncovered top-level parameter.

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 reduces to the HTTP method and path plus 'Test SRR Matcher', which merely restates the tool name. It never states what SRR means, what 'testing' entails, or what the tool validates, so an agent cannot form a concrete purpose from it.

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?

There is no statement of when to use this tool, when not to, or which sibling/debug alternative to prefer. The 'Tags: System Controller' fragment is grouping metadata, not usage guidance.

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