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

The description adds substantial context beyond the annotations: it discloses that a fresh single-use invite replaces any earlier unused one, that the requester is notified in their own Space, that answering requires invite rights, and which modes are read-mostly vs non-idempotent. That is precisely the kind of consequence and permission information the annotations cannot express.

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 text is dense but front-loaded by action and wastes nothing; each clause conveys a distinct fact. It reads as a compact run-on, but no sentence is filler.

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?

With only two well-documented parameters and no output schema, the description covers invocation, prerequisites, side effects, and notification behavior. Return values are not described, but the description does say what you get (an invite), which is sufficient for an agent to call it 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 100%, so the baseline is 3; the description goes further by explaining what each action value does and where a valid request_id comes from ('from action=list or the note posted in this Space'). That adds real meaning over the terse schema descriptions.

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 names the resource (join requests) and breaks it into four explicit modes, each with a distinct verb and outcome: 'action=mine', 'action=list', 'action=accept or decline'. An agent can tell this apart from siblings like list_requests or request_to_join because the modes and their effects are spelled out.

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?

Each action's purpose is spelled out with the condition that selects it, and a prerequisite is given ('Answering needs invite rights (project or full scope)'). It stops short of naming an alternative sibling tool, so the when-to-use-this-versus-another-tool guidance is implicit rather than explicit.

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