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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it explains the validation categories and that unreachable islands are 'detected by an actual graph traversal', plus the shape of each returned issue (stable process.* code, severity, message, suggestion). It does not discuss cost, limits, or side effects, but none are expected for a read-only validator.

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-loaded with the core action, then the category breakdown and return shape, then the usage trigger. The category enumeration is dense but each clause carries distinct information; no filler sentences.

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?

No output schema exists, so the description properly compensates by describing the returned issue structure and codes. With read-only annotations covering safety and 100% schema coverage on params, the definition is close to complete; minor gaps are the absence of explicit alternative/complementary validators and any mention of issue volume.

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 the two parameters (severityFilter, expectedProjectId) are already fully documented in the schema. The description adds no parameter-level detail (it never mentions the severity filter or project targeting), so the 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 ('Runs the BPMN-lite validation engine on the current process and returns the list of issues') and enumerates exactly what is validated across four named categories. The 'process'/'BPMN-lite' domain anchoring cleanly separates it from the sibling validators (validate_arch, validate_captable, validate_journey).

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 when-to-use guidance: 'Fits before presenting the diagram to the user, or when they ask check my process.' Clear context, but it names no alternatives and states no exclusions (e.g., when not to run it), 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.