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

This is an annotation contradiction: the annotations declare openWorldHint=true, but the description explicitly says 'no external research or outbound actions,' which contradicts the open-world annotation. It does add useful context about price, wallet authorization, and human review, but per the rubric the contradiction forces a score of 1.

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 description is four tight sentences, each with clear value: purpose, constraints, output, and payment/authorization. It is front-loaded and free of filler, making it appropriately sized for the tool.

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 paid, side-effecting service with nested input objects and no output schema, the description leaves significant gaps: no return format, no guidance on what the required brief must contain, and no explanation of the optional signature/idempotency fields. It covers core safety and price facts but is not complete enough for correct invocation.

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 compensate for missing parameter documentation. It only refers generically to 'buyer-supplied information' and never explains fields like brief, audience, source_text, payment_signature, idempotency_key, result_signature, or result_expires. Agents cannot infer correct parameter semantics from the description.

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 names a specific deliverable ('neutral interview questions') and the goal ('collect genuine customer outcomes and usable testimonials'), which clearly distinguishes it from sibling tools like discovery_questions or account_research_questions. The added constraints ('buyer-supplied information only', 'no external research or outbound actions') further sharpen its scope.

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 purpose statement implies when to use the tool: when neutral, testimonial-focused customer interview questions are needed. However, it provides no explicit when-not-to-use guidance and does not mention alternative sibling tools, so usage direction is only implicit.

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