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

With no annotations, the description carries the full burden, and it does add one genuinely useful behavior: a rate cap of 3 per day per account. However, it omits what happens at the cap (error vs. silent no-op), whether previously issued links are invalidated, and any auth/permission requirements for the caller.

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?

A single front-loaded sentence with the rate limit parenthetically placed; nothing is buried. The trailing 'Requires org_id and setup_claim' clause is redundant with the schema's required list and slightly dilutes the otherwise tight phrasing.

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 no-annotation, no-output-schema mutation tool with 0% parameter documentation, the description should explain the setup_claim source, error behavior at the rate limit, and side effects on prior emails. It supplies only the rate cap, leaving an agent unable to invoke this correctly on the first try without guessing.

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 0%, so the description must compensate and it largely doesn't: 'Requires org_id and setup_claim' only restates the required array. The critical opaque parameter 'setup_claim' — presumably the claim/token from account creation — is never explained, nor is its format or where an agent obtains it.

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?

Specific verb+resource: 'Re-sends the contractor's set-password email', which is clearly distinct from siblings like create_contractor_account or check_account_status. It doesn't explicitly name the sibling it relates to (the account-creation flow), but the action itself is 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?

Usage is implied by context (a contractor who hasn't completed setup), but the description never states when to prefer this over checking account status first or re-inviting via create_contractor_account. No exclusions or preconditions beyond org_id/setup_claim are given.

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