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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context: it returns session key and context, and clarifies that the session key is not an authentication credential or secret. It doesn't mention pagination or limits, but for a read-only list this is acceptable.

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 description is concise: three sentences with front-loaded purpose, output explanation, and a security clarification. Every sentence earns its place without redundancy or irrelevant detail.

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?

Given the tool's simplicity (one required parameter, full schema coverage, output schema present, and clear annotations), the description is complete. It covers what the tool returns and how to use the result, and does not need to explain return values because the output schema exists.

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 coverage is 100% with project_id described as 'the project.' The description reinforces the per-project scope but adds no format or lookup guidance beyond the schema. With the schema handling parameter semantics, a baseline score of 3 is appropriate.

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 clearly states the action ('List'), the resource ('a project's development sessions'), and the scope ('conversation threads'). It distinguishes itself from sibling tools by focusing on listing sessions and mentions that the returned session key is for use with dreamagent_chat and dreamagent_get_chat_status.

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 description explicitly explains when to use the tool ('select, continue, or monitor a specific development session') and references sibling tools for follow-up actions. It clearly positions this tool as the starting point for session operations, making the usage context unambiguous.

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