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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the read-only, closed-world nature is covered. The description does add real value beyond that: it flags the response as privileged, instructs the agent to follow the `privilege` block, and limits commits to deliverable.handling.safe_to_commit. It stops short of describing return structure or size.

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?

It is short with no filler, but it opens with a bare noun list instead of leading with what the tool does, and the parenthetical enumeration plus the privilege sentence read as a data dump rather than a front-loaded statement.

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?

For a read-only, two-parameter tool with no output schema, the description is partially adequate because it names the deliverable keys it returns and gives a privilege-handling rule. It still leaves 'status' and the shape of the privilege block unexplained, which matters given there is no output schema to fall back on.

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 only 50%: matter_token is documented as coming from request_engagement and needing secrecy, but matter_id has no description anywhere. The description adds no meaning about either parameter, so it fails to compensate for the coverage gap.

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 what the response contains (status, open questions, feature checks, deliverables) rather than stating a verb+resource, so the retrieval intent must be inferred from the title 'Get matter status and deliverables'. The listed contents also overlap with sibling tools named get_counsel_triggers and feature_check, leaving ambiguity about whether this tool surfaces those items or whether the siblings must be called separately.

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?

There is no guidance on when to call get_matter versus request_engagement, get_counsel_triggers, or feature_check. The only directive present concerns how to handle privileged output, not tool selection.

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