List Households Invitations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. "Get" implies a read-only operation, but the description does not explain scope, response format, pagination, authentication needs, or whether this returns all invitation tokens for the current household. It is not misleading, but it is very thin.

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 very short, but this is under-specification rather than effective conciseness. A three-word fragment does not provide structured or front-loaded information that helps the agent act.

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?

While the schema is simple and an output schema exists, the definition lacks essential context: no description of what invite tokens are, how they relate to households, or how this list operation differs from sibling invitation tools. An agent could not confidently select this tool without relying on the name and title alone.

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 0%, and the only parameter, accept-language, is undocumented in both the schema and the description. The agent receives no explanation of what this parameter controls or how to use it.

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 verb ("Get") and a resource ("Invite Tokens"), so the basic operation is somewhat clear. However, it is a fragment rather than a full statement, does not mention households or invitations, and does not clearly distinguish itself from the sibling creation tools like create_households_invitations and create_households_invitations_email.

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?

There is no guidance about when to use this tool versus creating invitations or listing other household resources. No exclusions, prerequisites, or alternative-tool routing are provided, leaving the agent to infer usage solely from the tool name.

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