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

Annotations already provide readOnlyHint and idempotentHint, indicating safe read operation. The description adds that the tool returns 'delivery stats', which is useful behavioral context beyond annotations. No contradictions.

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 a single sentence of 8 words, which is concise but loses accuracy by omitting the 'push' channel. It could include mentions of filtering and sorting without much bloat.

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?

Despite having 5 parameters and an output schema, the description only mentions channels and delivery stats, ignoring filter, search, sort, and limit capabilities. It is not complete for a list tool with multiple filters.

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 100%, so parameters are already well-documented. The description does not add new meaning beyond the schema, meeting the baseline of 3. It mentions 'delivery stats' which may relate to output, not parameters.

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 clearly states 'List marketing campaigns', specifying the verb and resource. It also mentions channels (email, SMS, WhatsApp) and delivery stats, distinguishing it from other list tools. However, it omits the 'push' channel present in the schema enum, making it slightly incomplete.

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?

No explicit when-to-use or alternatives are given, but the description implies usage for listing campaigns with delivery stats. Given it's a straightforward list tool, the context is adequate but lacks guidance on when not to use it, e.g., for detailed campaign analysis.

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