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 covered. The description's added value is the content-fidelity note that interactive figures are omitted while surrounding text is kept, which is genuinely useful but narrow. It says nothing about truncation behavior when max_chars cuts the essay short.

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 short sentences, front-loaded with the what and then the fidelity caveat. No filler or redundancy.

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 no output schema, the description usefully states the return format (markdown) and how figures are handled. What's missing is only how a truncated result is signaled or how to page past the max_chars cutoff, a minor gap for a simple two-parameter read.

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%, including slug-or-url format and the max_chars truncation semantics, so the schema carries the parameter burden. The description adds nothing beyond that, which is the baseline for full coverage.

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?

"Full text of one essay as markdown" names a specific resource (a single essay), the operation (retrieve full text) and the output format. The singular/complete-text framing implicitly separates it from list_posts and search, though no sibling is named explicitly.

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?

There is no statement of when to use this versus search or list_posts, and no prerequisites such as needing a slug obtained elsewhere. Usage is only inferable from the name and the required 'post' parameter.

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