get_invite_result

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Get detailed result,' which implies a read-only operation, but does not reveal any constraints, error handling, side effects, or what 'detailed' entails. For a tool with no 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 description is a single sentence with no extraneous words. It is efficient and front-loaded, communicating the core action and resource without fluff. Every word earns its place.

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?

The description is incomplete for an agent to call correctly. It does not explain what a 'detailed result' includes, how it differs from get_invite, or any error conditions. With no output schema or annotations, the description leaves many critical details undefined.

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?

The schema description coverage is 0%, so the description should compensate, but the only parameter (token) is a UUID that is self-explanatory by name and format. The description repeats 'invitation token,' adding minimal semantic value. Given the simplicity of the parameter, a baseline of 3 is appropriate, though no extra detail is offered.

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 verb ('Get') and resource ('detailed result for an invitation token'), which gives a basic sense of purpose. However, 'detailed result' is vague and does not clearly distinguish this from sibling tools like get_invite, which also deal with invitations. It is not a tautology but lacks specificity.

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 is provided on when to use this tool versus alternatives. There is no mention of when to prefer get_invite_result over get_invite, nor any conditions or exclusions. An agent receives no context to make an informed choice.

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