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 does disclose the cost (10 tokens) and the default-account fallback behavior. However, it does not elaborate on side effects such as sending duplicate invites (though the ignore_existing parameter implies a check), email delivery mechanics, or failure conditions. It is not misleading but leaves some behavioral aspects to inference.

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 three sentences: purpose, prerequisite/connection targeting, and cost. Each sentence earns its place with no fluff or redundancy. It is front-loaded with the action, then operational guidance, then cost.

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 the tool's simplicity, the presence of an output schema, and 100% parameter documentation, the description covers the essential aspects: what it does, the prerequisite call, how to choose the account, and cost. It lacks explicit mention of when not to use this tool versus alternatives, but the name and sibling context make that less critical. This is a solid, complete description for 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%, setting a baseline of 3. The description adds meaningful context for clerk_instance_id by explaining that it targets a specific connection and that omitting it uses the default account, which is not fully explicit in the schema description. It also instructs calling get_connected_accounts first, adding workflow context beyond the static parameter 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 first sentence 'Send an invite to the email address on a waitlist entry' clearly states the action and target resource, distinguishing it from sibling waitlist tools like delete_waitlist_entry and reject_waitlist_entry. The verb 'send invite' is specific and unambiguous.

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 usage context: 'Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account.' This gives explicit prerequisite and parameter-selection guidance. It does not explicitly mention alternatives or when not to use this tool, but the guidance is strong enough for an agent to know how to invoke it.

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