Pipeline commercial sur une période

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

The description states the tool returns a text runbook that the model must execute by calling other Boond tools, which is critical behavioral information beyond the annotations (readOnlyHint, destructiveHint, idempotentHint). No contradiction with annotations.

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 concise, comprising two sentences that efficiently convey the tool's purpose, use case, and return format. No extraneous information.

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 description adequately explains the tool's function, return type (text runbook), and its role as a prompt equivalent. Given the tool's complexity (3 parameters, no output schema), it is reasonably complete, though more detail on the runbook commands could be provided.

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%, with detailed explanations for each parameter (e.g., manager_id accepts ID or name with resolution). The description adds contextual value but does not significantly enhance parameter semantics 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 clearly states the tool analyzes commercial opportunities with closing in a given period, providing breakdown by state, weighted revenue, and top opportunities. The title 'Pipeline commercial sur une période' further clarifies the purpose.

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 description explains the tool is equivalent to the MCP prompt 'pipeline_commercial' and is useful for clients that cannot handle prompts correctly (e.g., claude.ai), providing clear when-to-use context. However, it does not explicitly mention when not to use it or compare with sibling tools.

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