Send Invite

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

The description discloses that it sends an email, triggers a notification, and returns a confirmation, adding value beyond annotations (which only indicate non-readOnly, non-destructive, non-idempotent). However, it does not explain what side effects occur (e.g., changes to user record), which is important for a PATCH endpoint. Annotations are not contradicted.

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 four sentences, front-loaded with the primary action. It efficiently includes context, required params, and API details. While it could be slightly more concise, all information is relevant and well-ordered.

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 tool's simplicity (2 params, no output schema), the description covers purpose, required parameters, and confirmation return. However, it lacks details on prerequisites (e.g., user must exist) and the exact nature of the 'confirmation' returned, leaving minor gaps.

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% with descriptions for both parameters. The description redundantly lists the required parameters but does not add semantic meaning beyond what the schema already provides, such as additional constraints or usage hints.

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 'Send invite email to specified user' and 'dispatch the notification or message related to Directory records,' providing a specific verb and resource. This differentiates it from sibling tools like send_punch_item_email by explicitly tying it to Directory records.

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?

The description says 'Use this to dispatch the notification or message related to Directory records' and lists required parameters, giving clear context. However, it does not explicitly state when not to use this tool or provide alternative tools among the many siblings, missing an opportunity for deeper guidance.

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