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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds one useful behavioral constraint — only 'published' documents are retrievable — which tells the agent non-published ids will fail, but nothing about error behavior or permissions. A 3 is appropriate given annotations carry most of the load.

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?

A single sentence with zero filler that front-loads the operation and enumerates the returned fields. Nothing could be cut without losing information.

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?

An output schema exists, so the description needn't document return shape, yet it does so briefly and harmlessly. Combined with the id-provenance hint and the 'published' constraint, an agent has everything needed to call it correctly; only explicit failure behavior 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?

Schema description coverage is 0%, but the sole parameter 'id' is given real semantic meaning: it is the identifier returned by the sibling search tool, which tells the agent where to obtain the value. That goes beyond the schema's pattern/length constraints alone.

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 ('Returns one published PreShiftIQ document') plus exactly what it yields (title, text, URL). It implicitly distinguishes itself from the sibling 'search' by tying the input to 'the id search returned', though it doesn't name an explicit alternative tool.

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 phrase 'by the id search returned' establishes the workflow context in which this tool is used, making the search-then-fetch sequence clear. There are no when-not-use conditions or explicit exclusions, but for a single-purpose lookup tool the context is adequately conveyed.

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