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

Annotations already declare readOnlyHint=true, so the description does not need to restate read-only behavior. The description adds value by disclosing ordering (new on top), offset semantics (offset 0 is fresh), and pagination via a hint at the end of the response. This goes beyond the annotation and provides useful behavioral context without contradicting it.

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 three short sentences, front-loading the purpose, then usage guidance, then pagination details. Every sentence earns its place with no filler or redundancy, making it efficient and easy to scan.

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 presence of an output schema and the readOnlyHint annotation, the description provides all needed context: what the tool returns (verbatim journal with session summaries and milestone notes), how to use it for a specific query, and how to paginate. No critical information is missing for an agent to call it correctly.

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 must compensate. It explains the offset parameter (offset 0 is fresh, then page via hint), but does not explain project_id. While project_id is likely self-evident, the description does not explicitly describe it, leaving a small gap in parameter documentation.

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 tool returns a project journal verbatim, listing content types (session summaries and milestone notes), and explicitly distinguishes from search_project by mentioning it for topic searches. The verb 'read' is implied but the resource and scope are specific, and the differentiation from the sibling makes the purpose 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?

The description gives explicit when-to-use guidance ('call for what happened N sessions ago') and points to the alternative for topic searches ('search by topic — search_project'). This is a clear directive that tells the agent exactly when to pick this tool over its sibling.

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