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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this with 'Does not save the reply,' which is consistent. It goes further by enumerating refusals (unmatched stored reply, unsaved refund/replacement/timeline, added stronger offers, closed case) and clarifies that a denial is not an offer. This is rich behavioral disclosure beyond the annotations, though it doesn't describe how partial or ambiguous matches are treated.

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 purpose is front-loaded in the first sentence, and the dense list of refusal rules each carries real behavioral weight rather than filler. It is on the longer side, but no sentence is redundant.

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 three-parameter validation tool with a read-only profile and an existing output schema, the description covers the domain rules an agent needs to interpret a verdict correctly. The main omission is its relationship to save_case and the overall review workflow.

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 3 parameters, so the description must compensate. It clarifies 'reply' as the outgoing public reply and 'caseId' as one review case, but says nothing about 'businessId' or format constraints. Baseline 3 is appropriate since it partially fills the gap but leaves meaningful parameter ambiguity.

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 (check) and resource (an outgoing public reply) scoped against one review case, so the agent immediately knows this is a validation gate rather than a write. It is clearly distinguishable from siblings like save_case and create_business, which persist data.

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?

The description implies usage as a pre-send validation step and ends with a concrete action rule: 'Do not send the reply when verdict is rejected.' However, it never names alternatives (e.g., save_case) or states explicitly when not to use it beyond the rejected-verdict case.

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