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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered; the description adds the non-obvious behavior that it 'Returns no steps when the workflow has no diagram yet' and resolves subWorkflowPageId nesting. No mention of pagination or result-size limits, but for a scoped read-only list this is solid.

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?

Front-loads the primary noun phrase (steps in diagram order) before field semantics, and each following sentence earns its place by decoding output fields. It is one dense run-on block rather than cleanly segmented, but with no output schema the field explanations are justified.

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 return-value burden and does so well, explaining unknown, uses, disputed, proposals, and variants. It stops short of describing the top-level response envelope, but an agent has enough to call and interpret the tool correctly.

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% for both parameters, so the schema already documents pageId and the workspace slug/default behavior. The description implies pageId ('a WORKFLOW page's steps diagram') but adds no syntax or format detail beyond the schema, so 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?

States a specific verb and resource ('Every step in a WORKFLOW page's steps diagram') and enumerates exactly what each step carries: phase, subWorkflowPageId, ownership claims, and `uses`. Precise scope makes it distinguishable from compass_priority_steps_find or compass_step_claims_list, though it never explicitly contrasts itself with those siblings.

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 concrete operational guidance on when/how to act on results: 'unknown: true ... those are the questions worth asking in an interview', 'A step with `uses` and nobody on it is one a system runs; don't ask who does it', and 'ask about disputed rather than picking a side'. It also names compass_process_diagram_ensure as the path when no diagram exists, though it doesn't frame a when-to-use-this-vs-that comparison among the listing siblings.

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