signupgenius_list_invited

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

Annotations already indicate readOnlyHint=true, and the description's 'List' is consistent with that. However, the description adds no extra behavioral context (e.g., whether only pending invitations are listed, return format, or other nuances). It does not contradict annotations, but provides no additional transparency beyond them.

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, clear sentence that immediately states the purpose. It is front-loaded and contains no unnecessary words or filler. 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?

Given the simple nature of the tool (no parameters, no output schema), the description is adequate. It clearly defines what the tool lists. The only minor gap is not clarifying the distinction from similar sibling tools, but that is more of a usage guideline issue. The core function is sufficiently described.

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 tool takes zero parameters, so the schema fully covers them (100% coverage). The baseline for zero parameters is 4, and the description does not need to explain parameter semantics since there are none. No additional meaning is required.

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 verb ('List') and the resource ('sign-ups the user has been invited to'). This directly distinguishes it from sibling tools like 'signupgenius_list_signedupfor' (sign-ups the user registered for) and 'signupgenius_list_created_active' (sign-ups the user created).

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?

While the meaning implies when to use it (when the user wants to see invitations), there is no explicit guidance on when not to use it or which alternative to choose. Given the close sibling 'signupgenius_list_signedupfor', the usage context is only implied rather than clearly differentiated.

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