remove_member

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

Discloses ownership requirement, but with no annotations the description carries full burden. Lacks details on destructive nature (irreversible?), side effects, or response behavior.

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?

Extremely concise – two short phrases. No redundant information, but arguably too brief for full clarity. A minor expansion on owner-only would improve without losing conciseness.

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?

Adequate for a simple parameterized tool with full schema coverage. However, lacks completeness on what happens upon deletion (e.g., data loss) and prerequisites beyond ownership.

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 baseline is 3. Description does not add any meaning beyond the schema; it just repeats the Japanese equivalents without clarifying formats or constraints.

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?

Description clearly states 'Remove a member from a sheet' (specific verb+resource). Distinguishes from sibling tools like add_member and update_member_role.

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?

Implies usage context (only owner can execute) but provides no guidance on when to use vs alternatives like update_member_role or no comparison with other member operations.

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