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

Annotations only flag non-read-only, non-idempotent, open-world; the description adds the actual mechanics: an AyHire email is sent, the recipient must sign in with that address to join, the link expires in 7 days, and re-inviting the same address mints a new link (explaining the non-idempotent hint). That is meaningful disclosure beyond structured fields.

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 core action and the ownership restriction are front-loaded, and every sentence carries information. The recipient-flow clause ('sign in with that address and join, then see its roles, picks and shortlist') is slightly padded but still useful for understanding the invite lifecycle.

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?

No output schema exists, and the description compensates by saying the invite link is returned and how long it lasts. Combined with prerequisites (owned, non-Personal workspace) and the send_email toggle, an agent has everything needed to call this 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 already 100%, so the baseline is 3, but the description adds value the schema lacks: the link is returned regardless of send_email, and send_email=false means link-only delivery. The workspace default and role semantics are left to the schema, which already handles them.

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?

States a specific verb and resource ('Invite a teammate by email into a workspace') plus the ownership scope ('a workspace you own'). This is clearly distinguishable from siblings like add_people_to_role (adding existing members to a role) and list_workspace_members without opening any schema.

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?

Gives real usage context: the workspace must be one you own and not the Personal workspace, and 'Pass send_email=false to only get the link' tells the agent how to vary behavior. It stops short of naming a sibling alternative (e.g., add_people_to_role for people already in the workspace), so it's clear context without explicit exclusions.

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