issue_certificates

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the delivery method ('via email (and WhatsApp if enabled)'), the plan requirement ('Requires PRO plan or higher'), and the return format ('Returns emission_id and status per recipient'). This adds useful context beyond the basic action, though it doesn't cover idempotency or error handling.

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 (three sentences) and front-loaded with the primary purpose. The subsequent sentences add essential behavioral details without unnecessary fluff. Every sentence earns its place, making it highly concise and well-structured.

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?

The description is fairly complete for a tool with three required parameters and no output schema. It explains the core action, return values, plan requirement, and delivery mechanism. However, it does not mention the recipients limit (max 500 in schema) or potential asynchronous behavior, which could be relevant for batch operations. The schema covers parameter details, but the description could provide more context on call behavior.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description does not add significant new meaning to the parameters; it only rephrases 'event' and 'recipients' without elaborating on badge_id or the structure of recipients. The schema already provides detailed parameter descriptions.

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 the tool's action with a specific verb ('Issue') and resource ('digital certificates') and adds context ('to a list of recipients for a specific event'). This distinguishes it from sibling tools like search_events or list_recipients, which serve different purposes.

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 description provides clear context for when to use the tool: issuing certificates to recipients for an event. It also includes a prerequisite ('Requires PRO plan or higher'), which is a form of guideline. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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