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

Annotations already flag destructiveHint=true, non-idempotent and non-read-only, so the safety profile is covered. Beyond that, the description adds real behavior: remove always produces a card and requires confirm only after the person confirmed, admin memberships can never be modified, and förening homes restrict leadership asks to adults. The only weak spot is the opaque 'done now; else a card' clause, which adds little clarity.

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?

It is short, but the structure is poor: sentence fragments and clipped phrases ('Run the place: done now; else a card', 'A förening: only adults' asks to lead') force the reader to reconstruct meaning. Conciseness is achieved at the cost of parseability, and the ordering does not front-load a clear statement of what the tool does.

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 five-parameter destructive mutation tool with no output schema, the description covers the available actions, the confirm flow and two authorization constraints. It leaves ambiguous what 'done now; else a card' means for the caller and does not describe what happens after each action, so it is adequate but incomplete.

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 80%, so most parameter meaning is already documented, and the description's main additions (roles are ids from list_members, confirm applies to remove) largely restate schema text. The claim that roles are 'ids from list_members' slightly muddies the schema's 'home's own role ids', so it does not meaningfully enrich parameter understanding.

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 concrete actions (accept_ask, decline_ask, set_roles, remove) and the resource (a member's place in a home), so the purpose is inferable. However, it is written in fragmented, telegraphic phrases ('Someone's place in a home they run') that never state a clean verb+resource summary, and the sibling relationship is only hinted at via 'ids from list_members'.

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 action-level guidance (use confirm: true for remove, set_roles takes ids from list_members) and two exclusion rules: only adults' asks to lead in a förening, and admins are never yours to change. It does not explain when to choose this tool over siblings like list_members or place_settings, and 'Run the place: done now; else a card' gives no actionable routing guidance.

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