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

The description usefully reinforces that the tool is non-executing ('opens nothing by itself'), which matches the readOnlyHint/openWorldHint=false annotations and clarifies a real ambiguity. Beyond that it discloses nothing about what the response contains in practice — whether it is a template array or a procedural walkthrough — so the key behavioral fact an agent needs is left unclear.

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, front-loaded with the resource, which is good. However the closing API note ('eDesk has a full REST API but no MCP server (checked 20 Oct 2026)') does not help an agent decide or invoke, and the middle sentence packs two conflicting claims into one clause.

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?

The tool is simple (no params, no output schema) and the description covers the non-destructive nature and the follow-on browser tools. What is missing is the crucial contract: the shape of what comes back. For a zero-argument tool whose whole value is the returned content, saying 'returns how to do it step by step' without clarifying it is not a template listing leaves a gap.

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 nothing for the description to disambiguate; baseline applies. The description correctly implies no inputs are required.

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 opening verb-and-resource ('List templates in the user's own eDesk account') is undercut by the very next clause, which says the tool 'Returns how to do it in eDesk step by step (screens, buttons, fields) and opens nothing by itself.' An agent cannot tell whether it receives a list of templates or a set of instructions for finding them, so the stated purpose is self-conflicting rather than specific.

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?

It does route the agent onward ('then do it with the cotlet_browser_* tools in the user's eDesk Cloud Browser'), which is genuine workflow guidance. But there is no statement of when to call this versus going straight to cotlet_browser_navigate, and no differentiation from sibling edesk_* tools. The final sentence about eDesk's REST API is background, not usage guidance.

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