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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context by defining what each funnel stage means and specifying that results include company name and domain when available, setting output expectations beyond the annotations. No contradiction detected.

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 compact and well-structured with clear labeled sections: core purpose, USE FOR, REQUIRED, REPORT TABS. Every section earns its place; there is no filler or repetition. The most important scoping decision (report tab meanings) is 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?

For a read-only report tool with fully documented parametersща, the description covers the essential invocation context: what the tool returns (funnel stage metrics) and which parameters are mandatory. The absence of an output schema is partly mitigated by the report tab definitions and the note about company name/domain, though a fuller return structure would be stronger.

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 baseline is 3. The description enhances this by explaining the semantics of each reportTab enum value (REACHED, ENGAGED, etc.), which the schema merely lists. It also highlights the three required parameters, making the call contract clearer.

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 opens with a precise statement of the resource ('Account-level funnel performance') and the tool's action (retrieve reports across stages). The title reinforces it as 'Get Account Funnel Stage Reports'. The list of REPORT TABS concretely defines the resource and distinguishes it from generic account stats or list tools.

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 'USE FOR' section explicitly enumerates four concrete use cases (progression, engagement/conversion analysis, social reach, pipeline/revenue tracking), giving the agent clear applicability. It does not name alternatives or exclusion conditions, but the directive list is sufficient for selection among siblings.

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