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

Annotations establish readOnlyHint=true, and the description adds useful behavioral detail: it discloses the return content (happy path step counts, median hours, deviating variants with missing/extra steps) and hints that deviations are candidate findings. This goes beyond the annotation without contradicting it.

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 description is a single, front-loaded sentence that immediately states scope ('Full process detail for one object type') followed by specific output elements. There is no filler, repetition, or unneeded detail.

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 single-parameter read-only tool with no output schema, the description conveys the key return elements and their meaning (happy path, deviating variants, findings candidates). It does not spell out the exact response shape or how to handle large variant sets, but that is a minor gap for such a simple interface.

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 sole parameter object_type already has a clear description with an example ('order'). The tool description reinforces 'one object type' but does not add new parameter syntax or format details, so the baseline of 3 is appropriate.

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 clearly identifies the tool as returning detailed process information for one object type, with specific content (step counts, median times, deviating variants). It distinguishes from the sibling list_processes by emphasizing 'one object type' and 'Full process detail', though it does not explicitly differentiate against get_object or get_metric.

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 'for one object type' implies this is the detailed single-process counterpart to listing processes, giving some usage context. However, there is no explicit guidance on when to choose get_process over siblings like get_object or list_processes, nor any exclusions or prerequisites.

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