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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the description's 'Read-only' tag is largely redundant. It does add value by disclosing the shape of the returned content (steps, connections, status, sprint/epic binding), but says nothing about pagination, error behavior for unknown IDs, or permissions.

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?

A single dense sentence, front-loaded with the core action and followed by the return-field inventory; there is no filler.

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?

There is no output schema, so the description must convey return contents, which it does via the enumerated fields. It is nearly complete for a simple one-parameter read, with only edge-case behavior (missing process, access limits) unexplained.

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% with a single required processId documented as a UUID, so the schema does the heavy lifting. The description adds no format, sourcing, or identifier-hierarchy guidance beyond the schema.

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 gives a specific verb and resource (full detail of one process model) and enumerates exactly what is returned: steps with name/type/role/duration, connections, status, and bound sprint/epic. This clearly separates it from list_processes and get_process_kpis 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?

The phrase 'one process model' combined with the required processId implies a fetch-by-id lookup, so usage is inferable. However, it never states when to choose this over list_processes, get_process_kpis, or list_process_insights, and gives no prerequisites or exclusions.

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