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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the join-link mechanism, the 14-day validity, the default role, the permission model, the confirmed-email requirement, and the 50-per-day rate limit. It also clearly states that calls from an agent's own turn are refused.

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 dense but well organized: purpose, role values, permissions and rate limit, then usage restriction and refusal behavior. Every sentence contributes operational information, and the main purpose is front-loaded.

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 no-annotation, no-output-schema mutation tool, this is nearly complete: it covers permissions, rate limits, invitation validity, role defaults, and refusal behavior. The main missing detail is the expected workspace identifier format and whether any success response or invitation status is returned.

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 0%, so the description must compensate. It explains the role parameter's enum values and default, and clarifies that invitation is by email to a workspace. It does not fully specify the expected format or source of the workspace parameter, which leaves a small gap.

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 verb and resource: invite someone to a team workspace by email. It also clarifies the invitation mechanism (Caddie emails a join link) and role options, so an agent can distinguish this from related tools like list_members or set_agent_access.

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?

It gives explicit usage constraints: only when the user asked for this person to be invited, only from a confirmed email address, and only by a workspace owner or admin. It also states a hard refusal condition for an agent's own turn and directs the agent to ask the user instead.

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