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

No annotations are provided, so the description carries the full burden. It transparently discloses return fields (id, email_address, status, created_at, revoked, total_count) and cost. It also reveals the prerequisite dependency. While it doesn't explicitly state it's read-only, the verb 'List' implies non-destructive behavior, and the cost disclosure adds context.

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 sentences with no redundant or fluffy content. It front-loads the purpose, then gives prerequisites, return fields, and cost. Every sentence earns its place.

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 complexity (list operation with filters and a multi-instance context), the description is complete: it covers purpose, prerequisite, targeting a connection, return fields, and cost. The output schema exists, so return values are further documented. It could mention pagination or error handling, but these are minor gaps.

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%, so all parameters are already described. The description adds a bit of context for clerk_instance_id (calling get_connected_accounts first), but this is also present in the schema. No significant new meaning is added beyond what the schema provides, so the baseline 3 applies.

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 it lists application invitations in a connected Clerk instance, using a specific verb+resource. It distinguishes from siblings like clerk.create_invitations and clerk.list_organization_invitations by specifying 'application' invitations.

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?

Provides explicit prerequisite: 'Call clerk.get_connected_accounts first.' It also explains how to target a specific connection (clerk_instance_id) or use the default. However, it does not mention alternatives like list_organization_invitations, so it lacks explicit when-not/alternatives guidance.

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