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

With no annotations, the description provides useful behavioral context: it requires a connected account, returns the updated waitlist entry, and states the token cost. However, it omits side-effect details such as whether rejection sends a notification, whether it is reversible, or any permission requirements beyond the connected-account prerequisite.

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 four short sentences, front-loaded with the purpose and including only necessary details: prerequisite, parameter targeting, return value, and cost. No filler or redundancy.

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?

For a two-parameter mutation with a full output schema, the description covers the essential ground: purpose, prerequisite, parameter selection, and return behavior. It could be slightly more complete by naming alternatives or side effects, but it is sufficient for an agent to invoke correctly.

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%, and the schema already fully describes both parameters, including the clerk_instance_id default behavior. The description restates the targeting logic but adds no new parameter-level guidance beyond what the schema provides.

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 opening sentence 'Reject a waitlist entry in a connected Clerk application' uses a specific verb and resource, clearly distinguishing this from related operations like invite_waitlist_entry and delete_waitlist_entry. The target object (waitlist entry) and scope (Clerk application) are immediately explicit.

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 gives explicit prerequisites: 'Call clerk.get_connected_accounts first' and explains how to select a connection via clerk_instance_id or default. It does not compare against sibling waitlist tools, but the context of use is clear and actionable.

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