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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds explicit behavioral context: 'Side effects: sends invitation emails' and the max-10-per-call limit. It also clarifies the prerequisite (pending and not joined). These details go beyond the annotations and are directly useful for the agent to anticipate consequences.

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, with purpose front-loaded, followed by the limit, the condition, an example, and the side effect. Every sentence earns its place, and there is no redundancy or filler.

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 simple single-parameter tool with an output schema, the description covers all necessary operational aspects: the action, the limit, the condition, and the side effect. An agent has enough information to call it correctly without missing prerequisites or consequences.

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 description coverage is 100%, with the parameter already documented as 'Email addresses with pending invitations to resend (JSON array). Example: ["pending@example.com"]'. The description repeats the array format and example, adding no new semantic information beyond what the schema provides. Baseline 3 is appropriate because the schema already carries the meaning.

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 states a specific verb ('Resend') and resource ('pending corporate member invitations by email'), and it distinguishes itself from sibling tools like invite-members (new invitations) and resend-fax (fax resending). The limit of 10 per call and the condition of pending/not-yet-joined add further specificity. It is clear 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 explicitly states when the tool works: only for addresses that were invited but have not joined. This is a clear usage condition. It does not explicitly name alternatives (e.g., invite-members for new invitations), but the condition and the context of pending invitations make the intended use evident. A small gap is not mentioning when not to use it (e.g., for already-joined members).

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