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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known; the description adds the substantive point that it 'opens nothing by itself', plus the fact that the official Zen Planner API is partner-only per Daxko docs, which explains why browser automation is the execution path. That is genuine context beyond the structured fields. It does not describe the shape of the returned guide (length, format, whether it includes URLs), which is the remaining gap.

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 workflow and no-side-effects points are front-loaded and earn their place, but the closing API-access paragraph is long, cites a dated documentation check ('checked 11 Oct 2026'), and could be compressed to one clause as the reason browser tools are required. The reference to 'ChatGPT, Claude or any AI agent' in the first sentence is filler that adds no decision-relevant information.

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 carries the burden of explaining the return value, and it does so: step-by-step screens, buttons, and fields. It also states the required follow-up step and the access constraint. Missing only specifics about the guide's format or whether it varies by account configuration.

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 schema semantics for the description to supplement. Baseline for a parameterless tool is 4, and nothing here misrepresents the (empty) input surface.

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 resource is clearly named (failed payments in the user's Zen Planner account) and the second sentence discloses that the tool returns step-by-step instructions rather than payment data. However, the opening sentence frames the tool as 'List failed payments ... from ChatGPT, Claude or any AI agent', which reads as if the tool performs the listing, so the description contradicts itself about whether this is a data-retrieval tool or a how-to guide. An agent must read both sentences to resolve the ambiguity.

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 explicitly routes the agent forward: the guide is obtained here, then executed with the cotlet_browser_* tools in the Zen Planner Cloud Browser. That is actionable sequencing against a named set of siblings. There is no explicit statement of when *not* to use it or how it differs from zen_planner_list_members, but the follow-up path is unambiguous.

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