tor_extract_posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds 'bounded page' but does not disclose ordering, exact page semantics, or whether it operates on the current thread/forum. With annotation coverage, the added context is modest but not misleading.

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 front-loaded sentence that communicates the essential purpose and scope. 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?

The tool is simple (2 optional params, read-only, has output schema) and the description covers core purpose. However, it lacks usage context versus sibling tools and enough parameter detail, making the overall package adequate but not fully complete.

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%, so the description must compensate. 'Bounded page' hints at limit/offset pagination, and the parameter names are self-explanatory, but the description does not explicitly explain units, maximum limits, or how offset relates to result sets. Minimal compensation only.

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 'Extract a bounded page of forum posts' names a specific verb (extract), a clear resource (forum posts), and the bounded/paginated nature. It also distinguishes from the sibling tool tor_extract_threads by targeting posts rather than threads.

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?

No guidance is given on when to use this tool instead of alternatives such as tor_extract_threads, nor any mention of typical scenarios, exclusions, or prerequisites. The description only states what it does, not when to choose it.

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