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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds only "for funnel setup," saying nothing about what data is read, whether results are paginated, or what a cursor does in practice.

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?

It is a single clause with no wasted words, but it is underspecified rather than concise — the brevity comes at the cost of any usable detail. Worth keeping, but it needs another sentence of substance.

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 and annotations carry some of the burden, but for a tool with a distinctive name and four close siblings, the agent still lacks what "Meta actions" are, what scope they cover, and when funnel setup should trigger this call.

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 0% for both parameters. The description never mentions limit or cursor, so any meaning has to be inferred from the conventional names alone; nothing is added about default page size or cursor lifecycle.

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?

"Read Meta actions for funnel setup" gives a verb (read) and an object (Meta actions), but "actions" is undefined and the funnel-setup qualifier doesn't clarify scope. With siblings like products_get_funnel_candidates and products_get_funnel_values sitting right next to it, an agent has no basis to tell what this returns versus those.

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?

There is no statement of when to call this rather than products_get_funnel_candidates, products_get_funnel_values, or products_get_health. The phrase "for funnel setup" hints at a workflow but gives no selection criteria or prerequisites.

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