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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive flags. The description adds meaningful non-structured context: 'Members only' discloses an authorization requirement, and it enumerates what the return payload conceptually contains (conversation, open missions, resources, formed objects). It doesn't cover pagination, but the auth constraint and content shape are valuable additions beyond annotations.

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 a gloss of what a 'process' means, usage guidance, and access constraint. The em-dash phrase defining 'processes' is slightly verbose but earns its place by disambiguating a domain-specific term. The trailing docs URL is short and useful.

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 list tool with one fully documented parameter and annotations covering the safety profile, the description supplies everything needed: what it returns conceptually, when to call it, and who can call it. Only return-format/pagination details are absent, which is acceptable given the low complexity.

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 100% – projectId is fully documented in the schema as 'Rikma (project) id.' The description adds no syntax, format, or constraint details for the single parameter, so the baseline of 3 is appropriate when the schema does all the work.

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?

Specific verb (List) plus resource (a rikma's processes) with a clarifying definition of what a 'process' is ('open-ended threads... an approach to a partner, a launch, a funding attempt'). This distinguishes it clearly from siblings like startProcessTool, attachToProcessTool, and listProjectResourcesTool.

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?

Explicit when-to-use is given: 'Use it to see what is already in motion before starting something new.' This routes agents away from redundant creation calls and toward this reconnaissance tool, with no ambiguity about the trigger condition.

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