quire.updateOrganization

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

Annotations mark idempotentHint true, and the description aligns by describing idempotent operations (setting full list, incremental add/remove). It adds clarity on the three modes beyond 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?

One sentence clearly covers all operations. While slightly more structure could help (e.g., bullet points), it is concise and front-loaded with purpose.

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?

Lacks information on permissions (e.g., admin required) and return values. For a simple update tool, it covers the main behavior but leaves some context gaps.

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?

All four parameters have schema descriptions (100% coverage), but the description adds semantic value by explaining the relationship between 'followers' (replace) and add/remove operations, which is not fully captured in 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 tool updates an organization's followers, specifying three operations: replace all, add, or remove. This distinguishes it from sibling tools like updateProject, which handle different resources.

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 usage by listing operations, but does not explicitly state when to use this tool versus alternatives (none apparent), nor does it provide exclusions or prerequisites.

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