user_invitations_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Get detailed information' without addressing permissions, read-only guarantees, error behavior, or what 'detailed' includes. Beyond the inherent implication of 'get' as a read operation, it adds little behavioral context.

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, focused sentence with no redundant words. The '[Users/Invitations]' prefix provides helpful categorization, and the structure is appropriately front-loaded with the verb and resource.

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?

Despite the presence of an output schema, the description is very sparse: no annotations, no usage context, and no parameter semantics are provided. For a tool with 3 parameters and a specific invitation-scoped operation, the description leaves significant gaps in what an agent needs to invoke it confidently.

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 0%, and the description does not compensate by explaining any parameters. The phrase 'specific user invitation' hints at the required invitation_id, but parameters like include and visible_apps_limit are completely unexplained, leaving the agent without meaningful parameter semantics.

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 uses a specific verb 'Get' with a clear resource ('detailed information about a specific user invitation'), making the operation unambiguous. The phrase 'specific user invitation' effectively distinguishes it from sibling tools like user_invitations_list (listing) and user_invitations_create/delete.

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 explicit guidance is given about when to use this tool versus alternatives. The description only states what it does, leaving the agent to infer that it should be used when an invitation_id is available and detailed data is needed. It does not mention exclusions or alternative tools.

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