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

Annotations already declare the tool read-only and idempotent. The description adds valuable behavioral context by specifying that the text field is the full body rendered as Markdown with headings, lists, links, code, and inlined media preserved. This goes beyond a generic fetch description without contradicting the annotations.

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 tight sentences with no filler. The first sentence front-loads the core operation and source of the id; the second clarifies the return behavior of the text field. Every sentence earns its place.

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 only one parameter, read-only annotations, and an output schema present, the tool is nearly complete. The description explains what is fetched and gives the meaning of the text field. It could add an explicit pointer to fetch_many for multiple ids, but nothing essential is missing.

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 schema only provides the UUID format for id, with 0% description coverage. The description compensates by explaining that the id must be a Stashr bookmark id returned by search or list_bookmarks, which gives the parameter semantic meaning beyond its format.

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 and resource: 'Fetch the complete content and metadata for one Stashr bookmark id'. It also distinguishes the tool from siblings by emphasizing 'one' id and by noting the id comes from search or list_bookmarks, which suggests fetch_many is for multiple bookmarks and search/list are list-level operations.

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?

The description clearly establishes when to call this tool: after search or list_bookmarks, using a single returned bookmark id. It does not explicitly name fetch_many as the alternative for multiple bookmarks or state exclusions, but the context is clear enough for an agent to select appropriately.

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