update_invitation

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

Annotations indicate readOnly=false and destructive=false, and the description matches by stating it updates a role. No additional side effects, permissions, or consequences are disclosed, but the annotation coverage keeps this adequate.

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 brief and well organized, with param guidance in a bullet-like second line. No redundant or filler content appears.

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?

Since an output schema exists, return details are not necessary. However, the description omits key contextual guidance such as the distinction between hub-profile and workspace invitations and the effect of changing a role on an existing invitation.

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%, and the description compensates only for workspace_id and role_id, including role value mapping. hub_profile_id and invitation_id are left unexplained, leaving half the required parameters without added 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 action ('Update the role assigned to a pending invitation') and identifies the target resource clearly. It does not explicitly differentiate from the sibling 'update_workspace_invitation', but the invitation resource is obvious from the tool name and context.

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 param sourcing guidance for workspace_id and role_id values, but does not explain when to use this tool versus update_workspace_invitation or other invitation-related tools. It lacks explicit conditions or exclusions to guide tool selection.

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