check_pipeline

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: omitted keys surface as 'verify' rather than failing. It is silent on whether the call is purely read-only, whether it needs stored credentials to inspect storage/automation settings, and how the 'ranked' ordering is derived.

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 one-line purpose is front-loaded before the config breakdown, and every listed key maps to an otherwise undocumented field, so the bulk earns its place. The layout is a little ragged (the '...' in source types is vague) and could be tightened into a cleaner structured block.

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?

Return values need not be described since an output schema exists, and the description thoroughly fills the empty parameter schema. Remaining gaps are what 'verify' means in practice and whether the check is read-only, but nothing essential to invoking it is missing.

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 0% – the single 'config' parameter is an untyped object with additionalProperties true and no properties. The description compensates fully by enumerating every accepted key, its nesting, and allowed enum values (web_form|whatsapp|..., round_robin|fixed|none, zapier|make|n8n, etc.), which the schema alone cannot convey.

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 ('Check a structured lead-pipeline config') and names the concrete output ('ranked leak-risk list'), so the agent knows exactly what it gets back. It doesn't explicitly contrast itself with the sibling check_pipeline_description, so sibling differentiation is only implicit.

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 note that all keys are optional and omitted ones are reported as 'verify' gives some practical guidance on how loosely the tool can be called. However, there is no statement of when to use this versus check_pipeline_description or analyze_run_history, and no prerequisites are mentioned.

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