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

Discloses that batch counts against weekly invite limit and requires at least first name. Annotations indicate mutation (readOnlyHint=false) and not destructive. 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?

Two concise sentences, front-loaded with action and key constraints. No wasted words.

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 limits and key requirement, but omits return value, error behavior, and handling of duplicate or invalid entries. Adequate but not comprehensive given complexity.

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 0%, so description must compensate. It clarifies that each guest needs at least a first name and that event_id is required, but does not explain other fields (email, phone, tags, etc.). Partial compensation.

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?

Clearly states the tool bulk-adds up to 200 guests to a live event's guest list, distinguishing it from single add (add_guest) and other import tools. Verb 'import' in name and 'Bulk-add' in description align.

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?

Specifies prerequisites (must be host, need event_id) and implies use for bulk imports vs individual add. Could explicitly note when not to use, but covers key context.

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