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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety is covered; the description still adds value by disclosing the return payload shape (body, assignee status, due date, decision state, revision/event history) in the absence of an output schema, plus the project-wide sharing model. It does not say what happens when the UUID is unknown or the item is not visible to the caller.

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 first sentence is dense and correctly front-loaded, and 'Reads only.' is a useful early signal. The trailing sentence about a bare 'add a task' possibly targeting another app is family-level routing boilerplate that does not apply to a read-only open and dilutes the definition.

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 one-parameter read tool with no output schema and full annotation coverage, the description compensates well by enumerating returned fields and the sharing/visibility model. Missing only failure behavior for an invalid or inaccessible work item.

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 100% and the single parameter's schema description already tells the agent where to obtain the work_id (project_work_find, project_open, project_draft). The prose adds nothing about the parameter, so the baseline 3 for a fully documented single-parameter tool 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?

States a specific verb and resource ('Read one shared work item in full') and then enumerates exactly what 'full' contains: body, assignee and whether they answered, due date, decision state, revision and event history. This is clearly distinguishable from project_work_find (locate) and project_work_update (mutate) without opening either schema.

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?

Gives an explicit exclusion and alternative: private notes/tasks/preferences belong to notebook_* tools, and ambiguous 'add a task' intents may belong to another connected app, with the instruction to ask once and stay with the answer. The visibility rule ('use only for work the user means to be visible') is a real usage constraint. It does not explicitly contrast with project_work_find vs project_work_update, and the destination guidance reads as family-level boilerplate rather than guidance for a read-only open.

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