github_orgs_list_invitation_teams

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

No annotations are provided, and the description does not disclose behavioral traits. It does not mention whether the operation is read-only, requires special permissions, or what happens if the invitation does not exist. With no annotations, the description carries the full burden and fails to provide sufficient 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 sentence, which is concise but under-specified. It lacks detail needed to understand the tool's behavior and context. Conciseness should not come at the expense of completeness; here it is more of a deficiency.

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?

Given the absence of an output schema and the presence of many sibling tools, the description should explain the return format, required permissions, and how this tool differs from other list tools. It does none of these, leaving the agent with insufficient context to correctly select and invoke the tool.

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 100%, so the baseline is 3. The description does not add any meaning beyond the schema; it does not explain what 'invitation_id' refers to or how to obtain it. The pagination parameters are well described in the schema, so the description offers no additional value.

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 'List organization invitation teams' is basically a repetition of the tool name. It indicates a listing operation but does not clarify whether it lists teams associated with an invitation or lists invitations that are for teams. This ambiguity limits clarity; however, it does specify a verb and resource.

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 like github_orgs_list_pending_invitations or github_orgs_list_failed_invitations. The description provides no context about the tool's specific role or when it is appropriate.

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