create_team_invitation

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits like whether this sends an email notification, requires admin permissions, has rate limits, what happens if the user already exists, or if the invitation expires. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence with zero waste. It's appropriately sized for a simple tool with one parameter, front-loading the core purpose without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (success confirmation, invitation ID, error conditions), behavioral constraints, or side effects. The 'Qiita Team only' constraint is helpful but insufficient for full contextual understanding of this write operation.

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 100% with the single 'email' parameter fully documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema ('Email address to invite'). Baseline score of 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 clearly states the action ('Invite a user') and resource ('to the team'), with the specific constraint 'by email (Qiita Team only)'. It distinguishes from siblings like 'add_group_member' or 'list_team_invitations' by specifying it's for team invitations via email, but doesn't explicitly contrast with 'create_team_access_token' or 'delete_team_invitation'.

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 implies usage context through 'Qiita Team only', suggesting it's for team-specific invitations rather than general user operations. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'add_group_member' or prerequisites such as required permissions or team membership status.

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