invite-members-to-project

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

The description adds no behavioral context beyond the annotations: it merely restates the tool's purpose and does not mention side effects such as invitation emails, permission requirements, idempotency behavior, or response outcomes. Since annotations already indicate non-readonly, non-destructive, and non-idempotent behavior, the description provides no additional transparency.

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 concise sentence with no filler text and the key operation is front-loaded. It is appropriately minimal for a simple invitation tool, though it is minimal enough that it leaves behavioral and usage guidance to other fields.

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?

The tool is simple, the schema thoroughly documents all parameters, and the annotations cover the core action. However, with no output schema, no permission context, and no mention of related alternative tools, the description is adequate but leaves some operational context to inference.

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 input schema provides descriptions for all four parameters, including the either/or requirement for usernames and emails and the default roleSlugs default. Since schema coverage is 100%, the description itself does not need to add parameter detail and does not materially add meaning beyond the schema.

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 specific action (invite), a specific resource (members) and the target system (Infisical), so an agent can immediately identify what the tool does. It also distinguishes itself from all siblings, which cover secrets, projects, folders, and environments, none of which handle member 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?

The description does not explicitly state when to use this tool versus alternatives or when not to use it. The intended use case is implied by the phrase 'Invite members to a project,' and there is no closely related sibling tool, but no direct guidance is provided.

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