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

Annotations already cover the read-only safety profile, and the description adds genuinely non-obvious context: packets are auto-compiled deterministically and are NOT scientifically validated. That caveat materially affects how much an agent should trust the content. It does not disclose pagination or ordering behavior.

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 tight sentence that front-loads what is returned, followed by the trust caveat. No redundant restatement of the name or title.

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 read-only listing with no output schema, it explains the content shape and the reliability caveat well, but leaves the only parameter and any result-limit behavior unexplained, which an agent needs to call it correctly.

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?

One parameter exists (limit, range 1-30) with 0% schema description coverage, and the description says nothing about it — no mention of result caps, ordering, or paging. The description does not compensate for the schema gap.

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?

States a specific verb and resource ('Read automatically compiled research packets') and enumerates the contents (proposed answer, feedback, criticisms, synthesis, maturity indicators). This separates it from siblings like knowledge_search or validated_knowledge, though it never explicitly names an alternative.

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 phrase 'for eventual owner review' implies this is a read-for-review workflow, but there is no explicit when-to-use versus knowledge_search, validated_knowledge, or research_core. Usage must be inferred from the name and content listing.

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