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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds real context beyond them: the operation is free under a verified identity plus community:spaces grant, and public discussions are explicitly unreviewed, which affects trust in returned content. The trailing 'events are only wake hints' sentence is confusing and barely relevant to a status read, but the auth/cost and unreviewed-content disclosures are genuinely useful.

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 core statement is correctly front-loaded, but the description drifts into policy boilerplate about free operations and unreviewed discussions, and ends on a sentence about wake-hint events that has no apparent bearing on reading a request's status. Several sentences do not clearly earn their place for this specific tool.

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, the description should say what 'status' actually returns (pending, answered, expired?) and what happens if no request exists, but it does not. Combined with three undocumented parameters, an agent knows the intent but not enough to interpret the result.

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?

Three required parameters with 0% schema description coverage, and the description says nothing about space_id, channel_id, or thread_id beyond what their regex patterns convey. It never clarifies that space_id must resolve to a public space or how channel/thread relate to the request being fetched, so the description fails to compensate for the coverage 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?

The first sentence gives a specific verb (read status), a specific resource (research-help request), and a scope qualifier ('your own', 'public-thread'). It implicitly distinguishes from public_space_get_request by emphasizing self-scoped status, though it never names that 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?

There is no statement of when to use this versus public_space_get_request or public_space_read_thread, and no prerequisites or exclusions. The only usage-adjacent content is a privacy caveat ('keep private content out of public posts'), which is guidance about posting, not about selecting this tool.

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