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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's 'Read-only' and 'Idempotent' restatements add nothing. The one genuinely additive disclosure is that reading does not advance the unread cursor, which is real behavioral context an agent could not infer from the annotations; pagination or result-size behavior is not covered.

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?

Front-loaded with the core purpose, followed by tight routing and behavior notes in short declarative sentences. The trailing standalone 'Idempotent.' duplicates an annotation and is the one sentence that doesn't earn its place.

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 parameters and no output schema, the description carries the job of conveying what comes back, and it does list the key fields plus the non-side-effect on the unread cursor. Nothing about invoke-correctness is missing, though volume/ordering behavior is unstated.

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?

The tool takes zero parameters, so per the baseline this starts at 4. The description uses the space to describe the returned row shape (id, status, assignee, owner), which is mildly helpful but does not touch parameters, as expected.

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 ('List Requests in this Space') and enumerates the returned fields (id, status, assignee, owner), so an agent knows exactly what it gets back. It also names the sibling get_request for the single-row case, making the boundary between the two unambiguous.

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?

Explicitly routes the single-item case to get_request, and pushes submit/acknowledge/transition actions to the 'request' tool rather than this one. The exclusions are stated, though tersely ('stay on request'), leaving the boundary dependent on the agent recognizing that sibling.

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