apps__beta_testers__remove

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds the DELETE endpoint and 'Unlink' wording, reinforcing the destructive nature. However, it does not clarify that this only removes the relationship and does not delete the beta testers themselves, which is useful context not fully covered by annotations.

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 clear sentence with the endpoint appended. It is concise, front-loaded, and contains no redundant or filler content.

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 relatively simple relationship removal, the description plus schema and annotations provide sufficient context. It identifies the action, the resource, the endpoint, and parameter meanings. It could add a note that this is a relationship-only removal, but the word 'Unlink' already conveys that. The lack of output schema is not an issue.

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%: both 'id' and 'body' have detailed descriptions in the schema. The description does not need to add parameter info, and the baseline of 3 is appropriate when the schema handles it.

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 uses the specific verb 'Unlink' and clearly states the resource: 'beta testers from an app.' The endpoint further clarifies the exact relationship. This distinguishes it from sibling tools like beta_testers__apps__remove (which removes apps from a beta tester) and beta_groups__beta_testers__remove.

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?

The description implies the use case through the resource relationship ('from an app') but does not explicitly mention when to use this over alternatives. There is no guidance on when not to use it or mention of sibling tools for related operations.

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