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

Annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them, explicitly stating it 'opens nothing by itself'. It adds genuine value by describing the return content ('screens, buttons, fields'). The trailing note about Tripleseat's official REST API and lack of an MCP server is background trivia that does not inform invocation.

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?

Purpose and the guide-then-act workflow are front-loaded, which is good. However, 'from ChatGPT, Claude or any AI agent' is marketing filler, and the closing sentence about Tripleseat's REST API/OpenAPI spec and 'checked 17 Oct 2026' is irrelevant to calling the tool and dilutes the actionable content.

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 zero-parameter, no-output-schema guide tool, the description covers the essentials of what it returns and that it performs no mutation. It is incomplete on targeting (which lead the steps will cover, given no identifier input) and on any prerequisites such as being signed in to Tripleseat before invoking it.

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?

Zero parameters, so the baseline of 4 applies and there is no schema semantics to compensate for. The one residual ambiguity — how the tool knows which lead to turn down given no lead identifier — is left unaddressed, presumably relying on session/user context, but that is not stated.

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?

Names a specific verb and resource ('Turn down lead') plus the scope ('in the user's own Tripleseat account'), and immediately clarifies the deliverable is a step-by-step guide rather than an executed action. This lets an agent distinguish it from sibling action tools like tripleseat_convert_lead_to_event or the cotlet_browser_* primitives.

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?

Explicitly states the workflow: read the returned steps, then perform them with the cotlet_browser_* tools in the Cloud Browser. That is clear conditional guidance. It stops short of stating when NOT to use it (e.g., to convert a lead instead of turning it down), so it is not a full 5.

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