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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavioral detail beyond that: hand-over links transfer KEY succession so 'you take over its role, and it leaves'; asks may not be decided before the RUN ends, so you must save request_id; leave does not touch posted content; set_name has a character constraint. It does not discuss rate limits or auth scope, keeping it from a 5, but it substantially enriches the mutation/destructive profile the annotations flag.

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 dense paragraph that front-loads the core membership concept, but it reads as a run-on blend of action definitions (join, look, accept, decline, withdraw, leave, set_name) with limited visual separation. Every sentence conveys useful information, but the lack of structure makes it harder to scan for a specific action, costing clarity.

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 seven-action mutation tool with destructive annotations and no output schema, the description covers the key behavioral risks: succession transfer on hand-over links, deferred ask decisions requiring request_id and mailbox polling, non-destruction of posted content on leave, and set_name character rules. It omits what a successful join returns and any error or rate-limit behavior, which would be needed for full completeness.

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 50%, with two of eight parameters fully described and two partially implied. The description adds functional semantics for several params (code as invite/hand code, link format and read-only usage, message as justification, offer_id from mailbox, peer_name constraints) but leaves name and request_id without explicit format or sourcing detail in the description, and name has no schema description either. This is better than schema alone but does not fully compensate for the coverage 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 clear multi-action purpose: join/leave a SPACE, answer roles, and manage membership across seven action modes. It distinguishes membership flow from read-only siblings (schellingaf_read_space, schellingaf_spaces) by emphasizing 'Finding a SPACE grants no membership.' However, it does not explicitly contrast itself against those siblings by name, so it falls short of a 5.

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 when-to-use guidance for each action: 'join when your task needs the SPACE,' 'look: what a link gives, before you use it,' 'accept and decline: a role offered to you,' 'withdraw: take back an ask nobody has decided,' 'leave: give up your own membership.' It also explains the open SPACE case ('POST. join') and the invite-link-vs-name-alone conditions, leaving little ambiguity about which mode to pick.

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