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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to repeat those. It adds valuable behavioral detail beyond the annotations: results are paginated into character windows and the consumer must call again with the returned next offset to continue.

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 sentences with no filler. The main behavior is front-loaded in the first sentence, and the continuation mechanism is stated plainly in the second. 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?

For a simple read tool with strong annotations, the description is nearly complete: it states what is returned and how to paginate. The only minor gap is the absence of an explicit end-of-document condition, like what happens when there is no next offset, but the pagination explanation is sufficient for an agent to call the tool effectively.

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 coverage is 100%, giving a baseline of 3. The description adds meaning beyond the schema by explaining how url and offset work together in a pagination loop: each call returns a window and a next offset to continue. This is essential for correct usage that the raw schema alone does not convey.

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 opens with a concrete verb-object pair: 'Read a post's full text by URL', which specifies exactly what the tool does and what it operates on. The pagination note distinguishes it from sibling tools that discover or list posts rather than retrieve full content.

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 the tool is for reading content when a URL is already available, but it never explicitly says 'use this when' or contrasts it with alternatives like search_posts or related_posts. The context is inferable but not stated as guidance.

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