system_srr_matcher

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing it as a safe read operation. The description adds that it validates the config against the panel matcher, implying a dry-run check, but it does not disclose what is validated, what the result looks like, or any failure behavior.

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 with no waste. The validation purpose is front-loaded, followed immediately by the critical input-format clarification.

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?

Given the nested schema and no output schema, the description should explain what a validation call returns (e.g., a boolean, error list, or validation report) and ideally clarify what the 'panel matcher' entails. These omissions leave an agent unsure about the outcome of the tool call.

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%, so the description must carry the burden for the single parameter. It explicitly states 'The body is the full responseRules config object, not an input string,' which correctly sets expectations for the responseRules parameter and prevents passing a string. The nested schema itself provides the structure, so this is sufficient.

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 'Validate' and resource 'subscription response rules (SRR) config' with the context 'against the panel matcher'. It is clear enough to distinguish from most siblings, though 'panel matcher' is not defined and no sibling is named as an alternative.

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 on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only clarifies the input format, which is parameter semantics rather than usage guidance.

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