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

The annotations already disclose that this is a non-read-only, open-world, non-idempotent operation. The description adds valuable behavioral context beyond annotations: the owner-only constraint for admin invitations, the need to confirm recipient and grants, and the uncertain-delivery guidance not to resend blindly. It does not cover rate limits or invite expiration behavior, but it meaningfully supplements the annotations.

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 compact and front-loaded: it opens with the core action, then adds permission, confirmation, and failure-handling guidance. Every sentence contributes operational value with no wasted exposition.

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 four-parameter mutation tool with open-world behavior and no output schema, the description covers the essential invocation context: what it does, who can do it, what to confirm, and what to do after uncertain delivery. It omits return-value details and invite lifecycle behavior, but those gaps are secondary for correct 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 description coverage is only 25%, so the description must compensate for undocumented parameters. It does add meaning for email and workspace grants, and clarifies that only an owner may invite a company admin, but it does not explain accountId, accountRole beyond the admin case, or the roleSlug options. The schema handles enums and patterns, but the description only partially fills the coverage gap.

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 and resource: sending an Agency team invitation with explicit client workspace grants. It is clearly distinct from sibling tools like company_resend_invitation and company_accept_invitation, and the mention of company_list_team further clarifies the intended workflow.

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 useful usage context: owner-only permission for inviting a company admin, confirmation of recipient and grants, and a caution against blindly resending after uncertain delivery in favor of inspecting company_list_team. It stops short of explicitly stating when to use company_resend_invitation versus this tool, so it is strong but not fully exhaustive.

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