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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds useful context beyond that: the response is Markdown and includes the date plus both the site and original LinkedIn links, which tells the agent what it will actually get back.

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 compact sentences with no filler; the core action and its outputs are front-loaded before the argument-sourcing hint. Every clause carries information the agent needs.

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, and the description compensates by enumerating the returned fields (full Markdown text, date, site link, LinkedIn link). Combined with the id/title sourcing note and rich annotations, nothing needed to call this one-parameter read tool correctly 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?

Schema description coverage is 100% and the single parameter is fully documented as 'Essay id (from search_essays) or its title'. The description restates the same dual-acceptance rule (id or title) without adding syntax, format, or fallback behavior, so the baseline 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?

The description names a specific verb and resource ('Get the full text of one essay by Niels Langereis') and even enumerates the returned components (Markdown text, date, site link, LinkedIn link). It is clearly distinguishable from the sibling search_essays, which handles discovery rather than retrieval.

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?

It tells the agent exactly where the argument comes from ('Use the id from search_essays, or a title'), which is genuine routing guidance toward the sibling tool. It does not state any when-not-to-use condition, but for a simple single-record fetch there is little alternative to exclude.

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