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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description reinforces that with 'opens nothing by itself,' which resolves the tension between the verb 'edit' in the name and the read-only annotation. It also discloses the response shape (screens, buttons, fields). The closing note about SmugMug's REST API v2 and the absence of a hosted MCP server is background context rather than behavioral information an agent needs before calling.

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 operative content is front-loaded and takes only two sentences: what it returns and which tools to use next. However, 'from ChatGPT, Claude or any AI agent' is promotional filler, and the final sentence about API v2 and the MCP server check does not help an agent decide or invoke and could be dropped.

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, the description carries the burden of describing the return value, and it does so concretely (step-by-step screens, buttons, fields). It also covers the follow-up path via browser tools. For a zero-parameter, read-only guide tool this is nearly complete; only the missing differentiation from other smugmug_* guide siblings is 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?

There are zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter information is missing because the schema is an empty object.

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 description names a specific resource (captions and keywords) and, crucially, states that the tool returns step-by-step instructions rather than performing the edit: 'Returns how to do it in SmugMug step by step (screens, buttons, fields) and opens nothing by itself.' This disambiguates it from the cotlet_browser_* execution tools. The opening clause ('Edit captions and keywords in the user's own SmugMug account') reads slightly like the tool performs the edit, but the following sentence corrects that.

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: use this to get the procedure, 'then do it with the cotlet_browser_* tools in the user's SmugMug Cloud Browser.' That is a clear when-and-how. It does not state when NOT to use it versus the sibling smugmug_* guide tools (create_gallery, change_gallery_privacy), though those cover different tasks.

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