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

Annotations only say this is a non-read-only, non-idempotent, open-world write. The description adds substantial context beyond that: the invite is pending until acceptance, the link expires in 24 hours, the invitee starts with calendar-only access, additional access is granted elsewhere in the dashboard, and the email is dispatched immediately on call. That is exactly the side-effect detail an agent needs before invoking.

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?

Four dense sentences, front-loaded with the core action, then the alternative, then access scope, then the immediacy warning. Every sentence carries distinct information, though it runs slightly long for a single tool description.

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?

With an output schema present, return values need not be described. The description covers the action, the alternative, the timing/expiry behavior, the default permission scope, and the pre-call check — 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 only 40% (role and timezone are documented; email, firstName and lastName are not). The description only touches the email parameter indirectly ('check the address with the user first') and adds nothing about name fields. Since the undocumented params are largely self-explanatory, this is adequate but does not fully compensate for 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?

States a specific verb (emails an invitation) and resource (team member / Nexwin account) with a clear outcome: they get their own login and become a member on acceptance. It explicitly distinguishes itself from the sibling add_team_member by contrasting the two use cases.

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?

Names the alternative tool (add_team_member) and the exact condition that selects it ('a person who only needs to be bookable and won't sign in'). It also gives an operational precondition: check the address with the user first because the email sends immediately.

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