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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavioral context beyond them: the status counts cap at 100 and only up to 20 instances are returned, which tells the agent results may be truncated. It does not mention permissions or error behavior, but those are minor for a read-only dashboard.

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?

Three short sentences, front-loaded with the usage trigger, then the return shape, then the exclusion. Every sentence carries distinct information with no repetition or padding.

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 single-parameter read-only tool with an output schema and full annotation coverage, the definition supplies the usage trigger, the return shape, the truncation limits, and an exclusion. Nothing an agent needs in order to call this correctly 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 description coverage is 100% and there is only one required parameter, projectId, so the schema carries the burden. The description adds no format, ID-source, or lookup guidance beyond what the schema already states, so the baseline 3 applies.

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 concrete verb and resource ('quick overview or dashboard of one Wapiworld project's WhatsApp numbers') and enumerates the card contents, so the agent knows exactly what comes back. It partially differentiates from siblings via the 'one project' scope and the explicit 'Not for sending a message', but never contrasts itself with list_instances or list_projects, which return overlapping data at a different granularity.

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?

'Use this when someone wants a quick overview or dashboard' gives a clear triggering intent, and 'Not for sending a message' supplies one exclusion. However, the real ambiguity for this tool is overview-vs-list (list_instances, list_projects) and that boundary is left unaddressed.

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