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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds useful content-level context (that passages are returned word for word with § addresses and that changes-since-receipt are included), but says nothing about ordering, volume, or scope of the aggregate.

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?

A single sprawling run-on sentence chained with semicolons and commas, with no front-loaded statement of what the tool is. The four concerns are buried rather than structured, forcing the agent to parse rather than 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?

An output schema exists, so return-shape explanation is not required, and the description does cover the conceptual contents. But for a multi-part aggregation tool with no required params, the description leaves unclear how the parts relate, their ordering, and how this call differs from the several sibling reads that surface the same objects.

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% and the single optional 'project' parameter is fully documented in the schema, including its slug source and the §-address/one-project exceptions. The description contributes nothing about the parameter, so the baseline 3 applies.

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 enumerates specific content (verbatim passages with § addresses, changes since receipt/agreement, open notes, handouts with answers), so an agent can infer this is a personal dossier/aggregate read. However, there is no clean verb+resource statement, and the four bundled concerns overlap heavily with siblings like part, what_changed, agreed, and hand_out, so the boundary is blurry.

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?

No when-to-use, when-not-to-use, or named alternatives appear anywhere. The agent must guess whether to call my_parts versus what_changed or agreed for the same information, which is exactly what usage guidance should resolve.

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