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 explains that the action only stages a request, that the owner must approve it in a browser with their agent PIN, that the invitee receives an emailed link, and that the invitee follows the default access role until moved. It also includes a critical safety instruction: never ask for or accept the PIN in chat.

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 compact and front-loaded with the core purpose. Each sentence earns its place: the first states what the tool does, the second explains the post-approval flow, and the third clarifies the staging behavior and PIN safety rule. There is no filler or redundancy.

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 three parameters, no output schema, and no annotations, the description is complete enough for correct invocation. It covers ownership requirements, role options, the approval workflow, what happens after approval, and a security constraint. No critical operational detail appears to be missing.

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%, so the baseline is 3. The description adds meaningful context beyond the schema by specifying that the workspace must be owned by the caller and that roles are assigned as part of the staged invitation. It reinforces the role parameter and the workspace ownership condition without repeating schema details.

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 opens with a specific verb and resource: 'Invite someone to a workspace you own by email, as a member, admin or owner.' It clearly distinguishes this from direct membership management by explaining that it only stages a request requiring owner approval, which separates it from siblings like set_member_workspace_role or remove_member.

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 clearly states the context: use this when inviting someone to a workspace you own, and it explains the approval flow. It does not explicitly name alternatives like cancel_invitation or set_member_workspace_role, but the ownership and staging language provides enough context for an agent to select it appropriately.

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