Submit an authorized text testimonial

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the mutation risk is covered structurally. The description adds non-obvious behavioral context the annotations cannot convey: that local command approval and actual customer public-use consent are separate, independently-required permissions — a meaningful authorization disclosure for a write 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?

Two tight sentences with zero filler; the core action is front-loaded and the consent clarification follows immediately. Nothing is repeated from the title or schema verbatim.

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 14-parameter, nested-payload mutation with no output schema, the description covers the critical consent semantics but omits the mutually-exclusive input modes (payload vs. payload_file vs. flat body flags), the role of the required payload.name/testimonial fields, and any contrast with sibling testimonial submission tools. Adequate but leaves several agent-relevant gaps.

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 71% and the schema itself already documents the confirm/customer_consent split and the payload vs. payload_file exclusivity. The description reinforces the consent distinction but adds no format, cardinality, or naming detail beyond the schema, so the baseline of 3 is appropriate.

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 states a specific action ('Import a real authorized customer statement'), which maps clearly to creating a text testimonial record. It is distinguishable from submit_video_testimonial by subject matter, but it never explicitly names or contrasts with any sibling tool.

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?

It gives real guidance on the two consent concepts (local confirm for the API call vs. customer_consent/payload.confirm for public-use permission), which is implied usage context. However, it never says when to choose this tool over submit_video_testimonial, submit_testimonial_batch, or preview_testimonial_batch, nor does it state prerequisites or exclusions.

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