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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and non-open-world, so the safety profile is covered. The description repeats that ('Read-only diagnostic only') rather than adding new behavior, though listing the diagnostic dimensions tells the agent what reasoning is exposed. No rate limits, auth requirements, or failure modes are disclosed.

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?

Two tight sentences with the core purpose front-loaded and the read-only constraint appended. No filler or restatement of the tool name.

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?

An output schema exists, so return-value detail is rightly omitted, and annotations cover safety. But with 3 of 4 parameters undocumented and no routing guidance to sibling diagnostic or retry tools, the definition leaves real gaps for an agent trying to call it correctly.

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 25% (just workspaceId). The description says 'one lead' but never disambiguates leadId versus profileUrl, which appear to be alternative lead identifiers, nor explains workflowId's expected format. Only workspaceId is documented, and that documentation lives in the schema, not the description.

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 ('Explain why one lead did or did not enter one workflow') and scopes it to a single lead/workflow pair, which distinguishes it from siblings such as campaignstack_trigger_workflow, campaignstack_retry_workflow_entries, and campaignstack_get_workflows. The enumerated analysis dimensions (score, dedup, exclusions, provider filters, verdict) make the output intent unmistakable.

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?

'Read-only diagnostic only' implies this is for investigation rather than mutation, which is useful framing. However, it never says when to reach for this versus trigger_workflow, retry_workflow_entries, or get_workflows, nor does it state prerequisites. Usage is implied, not specified.

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