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

With no annotations, the description carries the burden of behavioral disclosure. It does state two key non-obvious behaviors (no external message, no enrollment). However, it omits details such as permission requirements, idempotency semantics (despite the idempotencyKey parameter), inviter constraints, or what the response is. It adds some value but is not comprehensive.

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?

A single sentence that is efficient and front-loaded with the core action, then adds side-effect constraints. No waste, and the structure is clear and focused.

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 has 3 required parameters, a substantial sibling set, no annotations, and no output schema, the description is too sparse. It fails to explain parameter semantics, usage criteria, or potential side effects beyond the two mentioned. An agent would have to infer too much to call this correctly.

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%, so the description must compensate. It only hints that 'agent' is the invitee and 'cohort' likely refers to the `id` parameter, but it does not explicitly explain any of the three parameters, including `idempotencyKey`. The description adds minimal meaning beyond the raw 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 clearly states the action ('Invite a specific agent to a private cohort') and differentiates it by noting it sends no external message and does not enroll them. This distinguishes it from similar siblings like `invite_agent` or `accept_invitation` by specifying its exact scope and side effects.

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 usage (when you want a cohort invite with no external communication) but does not explicitly say when to use it over alternatives like `invite_agent`. It gives context but lacks explicit 'when-not' guidance or comparisons to sibling tools.

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