pylon_remove_issue_followers

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

No annotations are provided, so the description must disclose behavioral traits. It states the action 'remove' which is a mutation, but does not mention side effects, permissions, error conditions, or whether the operation is reversible. Minimal information beyond the basic action.

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?

A single concise sentence that communicates the tool's purpose without any redundant or unnecessary words. Very efficiently structured.

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 simple mutation tool with 3 parameters (1 required) and no output schema, the description is largely complete. It covers the action and the two types of followers to remove. Minor missing context like bulk behavior is provided by the schema. Adequate for the complexity.

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%, so the baseline is 3. The description adds context by naming 'team members' and 'customers' corresponding to user_ids and contact_ids, but does not add extra meaning or usage hints beyond the schema.

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 clearly states the verb 'Remove' and the resource 'team members or customers from following a Pylon issue'. It distinguishes from siblings like pylon_add_issue_followers and pylon_get_issue_followers explicitly.

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?

While the name and description implicitly indicate usage (removing followers when needed), there is no explicit guidance on when to use this vs alternatives like pylon_add_issue_followers or pylon_get_issue_followers. The context is clear but not explicitly stated.

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