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

Annotations indicate this is a write operation (readOnlyHint=false) and not destructive. The description adds useful context ('Spans all your events') and a prerequisite ('Requires a connected account'), but lacks details on error handling, idempotency, or behavior on duplicates.

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 concise—two sentences—and front-loaded with the main action. The first sentence efficiently lists key parameters. No redundant words, but the structure could be slightly improved by separating the prerequisite into a clearer note.

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?

Given 8 parameters and no output schema, the description provides enough context for basic use but omits return value, error conditions, and how the sponsor book relates to events. The scope statement helps, but more detail is needed for a fully informed decision.

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?

With 0% schema description coverage, the description partially compensates by explaining the tier enum values and mentioning total_committed. However, notes, contact_name, contact_email, contact_phone are not explained individually, only grouped as 'optional contact.'

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 action ('Add a sponsor to your sponsor book') and specifies key fields (company, tier, total committed, deliverables, contact). It distinguishes itself from sibling tools like 'add_vendor' by focusing on sponsors and mentioning scope 'Spans all your events.'

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 includes context ('Spans all your events,' 'Requires a connected account') but does not explicitly state when to use this tool versus alternatives. No 'when-not-to-use' guidance or comparison with related tools like 'accept_deal.'

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