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 covered. The description adds real value beyond that: the shape of the payload returned and the auth requirement ('Cotlet API key with access to this app'), which 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 return contents are listed twice nearly verbatim ('story text, place and coordinates, date, photo and video links' then 'full story, the place and its coordinates, the date and time, and links to every photo and video'), which is redundant. The sentence still front-loads the purpose, but a full sentence of duplication dilutes it.

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?

There is no output schema, so the description reasonably compensates by describing the returned fields, and it notes the auth requirement. For a one-parameter read tool this is nearly complete; only pagination/error behavior is left unaddressed, which is minor here.

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?

Schema coverage is 100% and the single parameter is documented ('Step ID from list_steps'). The description adds no further parameter detail, so the schema carries the burden and the baseline of 3 applies.

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?

States a specific verb ('Get') and resource ('step') and enumerates exactly what is returned (story text, place/coordinates, date, photo/video links). Saying 'Returns one step' distinguishes it from the sibling list_steps, so an agent can tell them apart without opening the schema.

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?

'Use it before editing a step or turning it into a post' gives clear positive context tied to siblings update_step and post creation. It stops short of naming the alternatives explicitly or stating when not to use it, so it falls just short of a 5.

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