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

Annotations only declare write/non-destructive/closed-world; the description goes well beyond by disclosing the actual side effects: Compass derives a level label, stores facts on the steps they concern (visible to every later reading of those workflows), raises open questions, and re-reads the priority. That is exactly the propagation and post-write behavior an agent needs to know before calling a mutation.

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?

Purpose is front-loaded in the first clause, and the sentence structure separates input, background processing, and usage trigger. The middle list of examples ('work still done on paper, and so on') is slightly loose but each item aids recognition, so little is wasted.

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 carries the burden of explaining what happens after the call, and it does: labels, step-attached facts, open questions, and a priority re-read. It stops short of stating return shape or error/permission conditions, but nothing essential for correct invocation is missing.

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%, so params are already documented (level meaning, said, priorityPageId, workspace). The description adds only a light gloss on 'said' ('in their words or a faithful summary'), which is useful but not beyond the schema's own description. 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 names a specific verb and resource: recording what a person said about one level of a PRIORITY's current transformations, and it enumerates the kinds of content (already do it, what rules it out, work on paper). It does not explicitly distinguish itself from near siblings like compass_transformations_make_change or compass_transformations_read, so an agent must infer the boundary, but the purpose itself is unambiguous.

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?

It gives a clear trigger: 'Use it whenever a conversation settles something about a level,' plus the rationale that the result lands on the priority's page rather than only the chat. It does not name alternatives or exclusions (e.g., when to use make_change instead), so it falls short of a 5.

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