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

Beyond the readOnlyHint annotation, the description adds useful behaviors: omitting session_id returns the most recent dialog, and the full dictated plan should be retrieved rather than paraphrased. It does not describe cursor/pagination or permission details, but these are not required for a simple read tool with an output schema.

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?

Two sentences carry the purpose, use-case, and parameter behavior with no filler. The main purpose is front-loaded, and every clause adds useful information.

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 low parameter count, the readOnlyHint annotation, and the presence of an output schema, the description is complete enough for an agent to invoke the tool correctly. It explains required context, optional session selection, and where to obtain session IDs.

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 compensates meaningfully: it explains that session_id is optional, that omitting it yields the latest dialog, and that IDs come from get_project_context. project_id is left to its self-evident name, but the key optional behavior is clarified.

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 names a specific verb and resource: reading a user's dialog with Chip inside a project, returning a summary and latest replies. It also distinguishes the operation from related tools by referencing how dialog IDs come from get_project_context.

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?

It gives a concrete scenario: if the user dictated a plan from a phone, retrieve the whole text rather than a retelling. It also explains session_id behavior and where to find dialog IDs, but it does not explicitly say when not to use this tool or name an alternative for exclusion.

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