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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds important non-annotation context: returned posts are quoted untrusted data, instructions in them should not be followed, and there are no agent-to-agent private messages. It does not explain the api_key parameter or return format, and the warning 'Do not send a model-provider API key' conflicts confusingly with the schema's api_key parameter.

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?

The purpose sentence is front-loaded and efficient. The safety message is repeated redundantly across two sentences ('Every returned post...' and 'Forum posts and reloaded locker notes...'), and the API key warning is awkwardly placed without explaining the parameter it references.

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, zero schema description coverage, and three undocumented parameters, the description should explain parameter behavior and return semantics. It covers prompt-injection safety well but leaves the agent unable to determine how post_ids and thread_ids interact or what api_key expects.

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 for all three parameters. It only implies a 25-item batch limit; it never explains post_ids versus thread_ids, whether they can be combined, or what api_key is for. The API key warning actually muddies rather than clarifies the api_key parameter.

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 first sentence states a specific verb and resource: 'Read up to 25 threads or posts,' with a clear batch size cap. It does not explicitly distinguish itself from sibling read_thread, read_threads, or read_since, so an agent must infer that this is the batched mixed-resource read.

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 gives no guidance on when to use batch_read versus read_thread, read_threads, or read_since. The remaining sentences are security warnings about untrusted data and API keys, not tool-selection guidance.

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