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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful behavioral detail that annotations cannot convey: the tool 'opens nothing by itself' and returns a step-by-step walkthrough with screens, buttons and fields. This output-shape disclosure is valuable given no output schema exists, though it could be stated more plainly.

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 core behavior is front-loaded, but the closing sentence about SmugMug's REST API v2 and the absence of a SmugMug-hosted MCP server ('checked 17 Oct 2026') is irrelevant to invoking this tool and dilutes the message. The middle clause chain ('Returns how to do it... and opens nothing by itself; then do it with...') is dense and would read better as separate short statements.

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 tool, the description does the important work of explaining what comes back (a step-by-step guide) and what happens next. The remaining gap is the unresolved tension between the 'list galleries' framing and the 'returns instructions' behavior, which an agent must guess about before calling.

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; the baseline for a no-parameter tool is 4. The description does not add confusing or fabricated parameter claims.

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 first clause say 'List galleries in the user's own SmugMug account', which is a clear verb+resource. But the second sentence says the tool 'Returns how to do it in SmugMug step by step (screens, buttons, fields)', which describes a guidance/instruction tool rather than a listing tool, leaving the actual output ambiguous. It also doesn't distinguish itself from cotlet_app_guide or the other smugmug_* siblings.

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?

There is a clear workflow handoff ('then do it with the cotlet_browser_* tools in the user's SmugMug Cloud Browser'), which tells the agent the next step. However, there is no guidance on when to choose this over cotlet_app_guide or the concrete smugmug_* action tools, and no preconditions or exclusions are stated.

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