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

Annotations already indicate this is a non-read-only, non-destructive, closed-world write operation. The description adds useful context by stating that nothing is for sale and that the tool only records the answer, preventing the agent from mistaking it for a real payment action.

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 front-loaded with the core question and the key caveat that nothing is for sale. The field list is dense but necessary given the schema's lack of descriptions, and it remains readable.

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 six-parameter survey tool with no output schema, the description covers purpose, behavioral caveats, and all parameter semantics. It could be improved with explicit sibling differentiation, but it is otherwise 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 carries the full burden. It documents all six parameters, including required fields, allowed values for would_pay and can_pay_now, payment method options, the max_price_usd range, and character limits for wanted_information and agent_name.

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: recording an answer to a would-you-pay survey about information from Tue. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools such as submit_or_answers.

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 clarifies that nothing is for sale yet and that the tool only records an answer, which implies it should be used for survey responses rather than actual payments. However, it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives.

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