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

The annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered by structured data. The description adds genuine value by stating the tool 'opens nothing by itself' and returns screens/buttons/fields text, which prevents an agent from assuming a data-fetch. The closing note about Teamleader's API v2 and lack of an official MCP server is accurate background but not behaviorally actionable.

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?

Three sentences carry the core message, but the first sentence spends words on the multi-host availability and the last sentence digresses into API versioning and an audit date that no agent needs in order to call the tool. The genuinely important fact — that this returns instructions, not data — should be front-loaded instead of appearing mid-sentence behind 'Returns how to do it in Teamleader step by step'.

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?

With no output schema and no parameters, the description has to carry the whole story, and it does cover the two-step workflow (get guidance, then drive the Cloud Browser). It is still unclear what the guidance text actually contains beyond a list of 'screens, buttons, fields', whether it depends on the user's account state, or how it relates to the cotlet_app_guide tool.

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?

The tool takes zero parameters, so there is no parameter meaning to add; the schema is complete for its scope and the description does not need to explain any inputs. Baseline 4 applies.

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 name and title say 'List quotations', but the description clarifies that it returns step-by-step instructions for how to do it in Teamleader rather than the quotations themselves, which is an important correction for an agent to catch. That clarification is buried after a marketing-style opening rather than led with, and the description never distinguishes this tool from the sibling cotlet_app_guide, which appears to serve a similar instructional role.

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 gives a clear follow-up path ('then do it with the cotlet_browser_* tools in the user's Teamleader Cloud Browser'), which tells an agent what to do next. It gives no when-not guidance and no comparison against cotlet_app_guide or the other teamleader_* siblings, so the choice between this and adjacent tools is left to inference.

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