Create Households Invitations Email

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 disclosing side effects and behavior. "Email Invitation" says nothing about whether an email is sent, whether state is mutated, whether the operation is destructive, or whether authentication is required. This is a significant transparency gap for a create-type tool.

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 two words, but this is under-specification rather than conciseness. It does not front-load any actionable information beyond what the title already conveys. A useful description would at least state that it creates an invitation email and mention required inputs.

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?

Even though an output schema exists, the description is completely inadequate for a tool with 3 parameters, 0% schema coverage, and no annotations. It fails to explain the purpose, when to use it, what the parameters mean, or what side effects occur, so an agent cannot confidently select or 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 description coverage is 0%, and the description "Email Invitation" adds no meaning to the parameters email, token, or accept-language. The agent cannot determine what the token represents, what format the email must take, or how accept-language affects the invitation.

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 "Email Invitation" is a noun fragment that restates the tool name without stating what the tool does. It provides no verb, no resource, and no explanation of whether it creates, sends, or manages an email invitation. It also fails to distinguish itself from the closely related sibling create_households_invitations.

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 alternatives such as create_households_invitations or list_households_invitations. The description gives no context, prerequisites, or exclusions, leaving the agent to infer the intended use 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.