bulk_invite

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the duplicate-skipping behavior, which is useful, but does not cover side effects (e.g., email sending via send_email), idempotency, permission requirements, or failure behavior. The disclosed behavior is positive but incomplete.

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 that front-loads the primary action. It is efficient and free of fluff, though it is possibly too brief to cover the necessary semantic load for the tool.

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?

For a tool with 4 parameters, no output schema, and no parameter documentation, this description is insufficient. It does not explain parameter meanings, return value, pagination, or error scenarios. Agents would need to inspect the schema and infer heavily.

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 mentions no parameters. The schema defines 'slug', 'candidates', 'send_email', and 'expires_days' with only type info, no explanations. The description offers zero value in understanding what these parameters control, leaving the agent to guess.

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 action 'Bulk create assessment invitations' and adds a distinguishing behavior 'skips duplicates', which separates it from the singular create_invite sibling. An agent can immediately understand what this tool does and how it differs from related tools.

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 implies bulk usage via the name and phrase, but gives no explicit when-to-use vs alternatives (e.g., create_invite for single). No when-not-to-use conditions or edge cases are mentioned. The guidance is implicit at best.

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