get_campaign_stats

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

No annotations provided, so description carries full burden. It discloses the read-only nature, auto-detection of sandbox mode, and the list of returned metrics. Lacks mention of permissions or side effects, but for a read operation the transparency is adequate.

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 sentences plus a bullet list showing metrics. Front-loaded with purpose. Could be more structured but is concise and to the point without fluff.

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?

Covers input parameters well and lists output fields despite no output schema. Does not mention error handling or performance, but for a simple stats retrieval tool it provides sufficient context for correct invocation.

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%, baseline 3. Description adds value by instructing to get campaign_id from send_sms result and noting auto-detection of sandbox, though the sandbox parameter's necessity is ambiguous. Overall adds meaningful guidance beyond schema.

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 starts with a clear verb ('Obtiene') and specific resource ('estadísticas de entrega de una campaña SMS'), listing the exact metrics. It clearly distinguishes itself from sibling tools like send_sms or list_campaigns by focusing on post-delivery statistics.

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?

States it works for 'campañas enviadas o completadas', providing clear context on when to use. Does not explicitly state when not to use or name alternatives, but the context is sufficient for an agent to infer appropriate usage.

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