decline_thread

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about refund possibilities and API key requirements, which aren't in the schema. However, it lacks details on side effects (e.g., thread status changes), error conditions, or response format, leaving gaps for a mutation 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?

The description is appropriately sized with three sentences that each add value: action definition, user roles/refund context, and authentication requirement. It's front-loaded with the core purpose. Minor room for improvement in flow, but overall efficient.

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 mutation tool with no annotations and no output schema, the description provides basic operational context (refunds, API key) but lacks completeness. It doesn't cover success/error responses, idempotency, or system state changes, which are important for an agent to use this tool correctly.

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 100%, so the schema already documents both parameters thoroughly. The description doesn't add any meaningful semantic details about the parameters beyond what's in the schema (e.g., format of thread_id, examples of reasons). Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Cancel or decline') and resource ('a thread on the402.ai'), making the purpose evident. However, it doesn't explicitly differentiate this tool from potential siblings like 'delete_service' or 'update_service' that might also modify thread states, missing full sibling distinction.

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 provides some implied context by stating 'Either the agent or provider can use this' and mentioning refund conditions, but it doesn't give explicit guidance on when to use this tool versus alternatives like 'accept_proposal' or 'send_message' for thread management. No clear when-not-to-use or alternative tool references are included.

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