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

Annotations include readOnlyHint=true and openWorldHint=true, but the description adds little behavioral context. It mentions 'Inputs are validated server-side' and 'audited deliverable', but does not disclose what happens to inputs, data handling, or any side effects beyond the read-only nature already hinted. No contradiction exists, but the added transparency is minimal.

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 short, but it is not well-structured. It opens with a French term that duplicates the tool name, then jumps to a reference case with specific metrics (€320k, 3 quick wins, 5 automations) that are tangential. The main purpose is buried in implication rather than being front-loaded.

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?

The tool has a complex schema with 7 parameters, including nested objects, and no output schema. The description is inadequate: it does not explain the deliverable structure, the meaning of the inputs, or when to use the tool. It provides almost no useful context for an AI agent to correctly select and invoke this tool.

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 only 14%, and the description does not explain any of the parameters. It only says 'send the documented case fields' without clarifying what those fields mean, how to structure topProcesses, or what values are expected. The description fails to compensate for the low schema coverage.

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 does not clearly state what the tool does. It says 'Mining des process' (French for 'process mining') and 'Returns a structured, audited deliverable', but the actual purpose (e.g., analyzing processes to identify waste) is only implied through the reference case '€320k gaspillage identifié'. The verb is missing, and the description does not distinguish it from sibling tools like process_mapping.

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?

No explicit when-to-use or alternative guidance is provided. The phrase 'Gapup agent-payable C-suite expertise (COO)' vaguely suggests executive use, but it does not explain when to choose process_mining over process_mapping or other similar tools. There is no exclusion or comparison.

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