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

Annotations already declare readOnlyHint=true and destructiveHint=false, which would look wrong for a tool named 'edit'; the description resolves that tension by stating it 'opens nothing by itself'. It also explains that the payload is step-by-step UI instructions and the actual mutation must go through browser tools. Missing only prerequisites (e.g., does the user need an open browser session or authentication).

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?

Two core sentences do the real work and the behavioral constraint ('opens nothing by itself') is front-loaded before the handoff to browser tools. The closing sentence about Tumblr's public API v2 and the absence of an official MCP server is justification trivia that a calling agent does not need to act.

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 definition covers what it returns, that nothing is executed, and which tools finish the job. It could be tightened with a note on how the target post is identified, but nothing essential for correct invocation is absent.

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 parameter meaning to convey and the baseline of 4 applies. The description correctly implies no inputs are accepted, since the post to edit is presumably identified elsewhere in context.

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?

Names the verb and resource (edit a post in the user's own Tumblr account) and then immediately corrects the natural reading by stating the tool returns step-by-step instructions rather than performing the edit. An agent can tell what comes back. It stops short of 5 because the leading sentence patterns like a write operation, so the true nature only becomes clear on the second clause.

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?

Gives an explicit workflow: call this first to get screens/buttons/fields, then perform the action with cotlet_browser_* tools in the Tumblr Cloud Browser. That sequencing is exactly what an agent needs. It does not say when to prefer this over other guided siblings such as cotlet_app_guide, leaving the boundary implicit.

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