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 meaningful behavioral context by explaining that 'SEO linked_article {id,title,content} adds the full Markdown article', which is not disclosed by the annotations. This goes beyond the structured metadata.

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 description is concise, leading with the core purpose, then adding relevant nuances about the SEO-linked variant and the editing sibling. It is front-loaded and every sentence carries information. A slightly tighter structure (e.g., separating the read-only note from the SEO variant) would be ideal, but it's still efficient.

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 simple read operation with a single parameter and no output schema, the description is complete enough: it states what it does, mentions a special case (SEO-linked article), and points to the editing sibling. The only minor gap is the lack of an explicit description of the return format, but given the straightforward nature, the information provided suffices.

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 input schema provides a full description for the only parameter output_id ('The output id (uuid)'), and the description does not add any extra semantic detail about the parameter. Since schema coverage is 100%, the baseline of 3 applies; the description only repeats what the schema already states.

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 states a specific verb ('Read'), a resource ('a queue draft'), and by 'id', making the purpose immediately clear. It also distinguishes itself from the sibling 'redraft_output' by noting that one edits while this reads, and mentions the SEO-linked article variant. This is well above the minimum viable clarity.

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 implies its role as a read-only counterpart to 'redraft_output' by saying that redraft_output edits the queue draft only. While it doesn't explicitly state 'use this when you need to read a draft' or list all alternatives, the context gives enough direction for a typical read vs. edit scenario. It doesn't mention when not to use it, but the implication is strong enough for a 4.

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