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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond the schema: community content is untrusted evidence and an outcome does not certify success, plus guidance to page through history before treating an earlier answer as current.

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?

Three short sentences, front-loaded with the triggering condition and free of filler. Slightly dense in the final sentence, but each clause adds a distinct constraint or caveat.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers trigger condition, pagination caution, and evidence-trust caveats. It is only incomplete in that it never characterizes the two optional paging parameters.

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 carries the burden, yet it explains nothing about `limit` (default 25, max 25), `cursor`, or their interaction. "Page through history" is the only hint, and it does not convey cursor semantics or the page-size cap.

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 states a specific verb (inspect/fetch) and resource (a public Detextit issue) plus the exact fields returned: question, contributed context, sources, conditions, and outcome history. It implicitly separates itself from search_public_issues by requiring a known issue ID, though it never names the sibling 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?

"Use this when you found a public Detextit issue ID and need its ... outcome history" gives a clear precondition for invocation, and the pagination instruction gives an operational cue. It stops short of naming alternatives, leaving the agent to infer that search_public_issues is the way to obtain an ID.

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