invite_guest_to_workspace

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Invite' implies a write/mutation operation, but nothing is said about whether this sends an email, requires the target to accept, is idempotent, what happens on duplicate invite, or what the return value is. For a mutating tool with zero annotation coverage, this is a significant gap.

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 single-sentence description is extremely concise and has no wasted words. It's not verbose, but it's under-specified rather than elegantly concise—brevity here is a symptom of missing substance.

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 an 8-parameter mutation tool with no annotations, no output schema, and only 25% schema coverage, this description is far from complete. It doesn't clarify what the guest's default permissions are, how optional booleans interact, the role of custom_role_id, or anything about the invite outcome/response. The agent would be guessing on 6 of 8 parameters.

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%, meaning 6 of 8 parameters (can_edit_tags, custom_role_id, can_create_views, can_see_time_spent, can_see_time_estimated, can_see_points_estimated) are completely undocumented in the schema. The description offers zero compensation for these. It doesn't explain what these boolean permission flags govern, the meaning of custom_role_id, or the relationship between the optional booleans and that role.

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 'Invite a guest user to a workspace' uses a clear verb (invite) and resource (guest user to workspace). It distinguishes reasonably from sibling 'remove_guest_from_workspace'/'get_guest' by the action verb, though it doesn't specify any nuance beyond that basic action.

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?

No guidance on when to use this tool vs alternatives. There's no mention of permission requirements, whether the invited guest must already exist, email domains, or how the guest flow relates to get_guest or remove_guest_from_workspace. The description provides no context for selecting this among the 100+ siblings.

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