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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely beyond them: the result is capped at 20 material changes and contains before/after claims with dated sources, and it will not perform new research or send notifications.

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 tight sentences, front-loading what is read before qualifying it with scope limits. No filler; every clause carries 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?

With no output schema, the description usefully previews the return shape (20 items, before/after claims, dated sources) and the no-side-effects boundary. It is only incomplete on the unexplained required parameter.

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?

There is one required parameter (opportunity_id) with 0% schema description coverage, and the description never mentions it. The gap is aggravated by a name mismatch: the tool is about 'project updates' but keys on an opportunity_id, and nothing explains that relationship.

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?

States a specific verb (Read) and resource (this workspace's watch status plus the latest 20 material changes, with before/after claims and dated sources). The scope is concrete, though it does little to distinguish itself from the near-named sibling get_account_changes.

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 clause 'Saved evidence only; no new research or notification' tells the agent this reads cached evidence rather than triggering fresh analysis, which is useful implied guidance. However, no alternative tool is named and no explicit when-not condition is given, so the routing must still be inferred.

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