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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with "opens nothing by itself," resolving the name/behavior mismatch. It adds useful context that the return value is a step-by-step procedure with screens, buttons and fields rather than a performed action. It stops short of describing format or length of that returned guide.

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 clarification and sibling routing are front-loaded, which is good. However, the first clause restates the name, and the final sentence about Flickr's official REST API and the absence of an MCP server is tangential justification rather than actionable guidance for invoking the tool.

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 guidance tool, the description covers what it returns and how to act on it, which is the essential information. The main gap is that it doesn't specify the shape or scope of the returned steps or confirm the no-argument invocation.

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 the baseline would be 4, but the description never explains why no arguments are needed—an agent may reasonably wonder how a photo is identified. It implies the tool is argument-free by describing it as a pure instruction lookup, but does not state that explicitly.

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 explicitly reframes the tool: it "Returns how to do it in Flickr step by step (screens, buttons, fields) and opens nothing by itself," which is critical because the name flickr_upload_photo implies a write action. It also routes the agent to the cotlet_browser_* siblings for the actual work. The opening clause repeats the misleading name, but the clarification lands immediately after.

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 gives a concrete workflow: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's Flickr Cloud Browser. What's missing is disambiguation from adjacent siblings such as cotlet_app_guide, cotlet_browser_upload, or cotlet_upload_file, so the agent must infer which guide source applies when.

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