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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful behavioral context that the default payload is 'compact' and that full evidence requires an opt-in flag, but it says nothing about pagination behavior despite limit/before/cursor existing, nor about failure or empty-result behavior.

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 short sentences, front-loaded with the action and followed by the conditional, with no filler. It is efficient, though the terseness borders on under-specification for a 5-parameter tool.

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 tool with 5 parameters, 0% schema coverage, no output schema, and no sibling differentiation, two sentences are not enough. An agent cannot tell what taskId filters, how cursor/before paginate, or how this read differs from the other read-shaped siblings.

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% across 5 parameters, so the description must carry the load. It explains the semantics of only one parameter (fields, contrasting 'compact' with 'full evidence'), leaving limit, before, cursor, and taskId entirely undocumented in both places.

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 verb+resource ('Read the compact change-and-work brief') is present, but 'change-and-work brief' is domain jargon that an agent cannot resolve against siblings like waystation_search or waystation_handoff_get. No differentiation from the seven sibling tools is offered.

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 second sentence gives a real when-condition for the fields=full mode ('only when full evidence is needed'), which is useful implied guidance for mode selection. However, there is no guidance on when to choose this tool over waystation_search or waystation_handoff_get, nor any mention of prerequisites.

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