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

Goes well beyond the annotations: discloses that access is inherited immediately, that explicit board membership overrides, that the member may create/move boards into the namespace, that 'owner' is structural and unassignable, and that the caller must be the workspace owner. These are non-obvious authorization and side-effect facts the agent could not infer from readOnlyHint=false / destructiveHint=false.

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?

Front-loaded with the core action and scope, then layers on inheritance, roles, and auth in dense, non-redundant sentences. The role sentence slightly overlaps the schema description, but nothing is padding.

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 non-idempotent mutation with no output schema, it covers authorization, side effects, and role constraints well. It does not say what happens if the user is already a member (relevant given idempotentHint=false) or how failures are reported, leaving one meaningful gap.

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 schema already documents slug format, username case-insensitivity, and the role enum. The description's role text ('owner' is structural and cannot be assigned) and 'existing user' largely restate the schema rather than adding new meaning, so it sits at the high-coverage baseline.

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?

States a specific verb and resource — 'Grant an existing user workspace-level membership (NamespaceMember row) in the namespace identified by its slug' — and distinguishes itself from sibling tools by emphasizing 'existing user' and 'Direct grant — no invitation to accept', which separates it from invite_board_member and add_board_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?

It establishes the precondition ('Requires the workspace owner'), the eligibility ('an existing user'), and rules out the invitation flow ('Direct grant — no invitation to accept'). It never names invite_board_member or add_board_member explicitly as the alternative for the other cases, so routing is implied rather than spelled out.

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