Edit group

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

No annotations provided, so description carries full burden. States it edits and requires verification code, but does not disclose behavioral traits like partial update behavior, idempotency, or side effects. Lacks detail for a mutation tool.

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?

Single clear sentence with no extraneous information. Efficiently communicates core purpose and a key requirement.

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?

Tool has 10 parameters, nested objects, and no output schema. Description is too brief to provide complete context on how edits work, partial updates, or return values. Inadequate for a complex mutation tool.

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 40%; description adds little beyond mentioning 'details and/or replaces its member list'. Does not elaborate on other parameters like name, clanChat, homeworld, etc. Fails to compensate for low schema coverage.

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 verb (Edits), resource (existing group), and scope (details and/or member list). Distinguishes from sibling tools like create, delete, add/remove members by implying this is for editing overall group.

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?

Mentions requirement of verification code but does not provide explicit guidance on when to use this tool versus sibling tools for adding/removing members individually. Adequate but lacks contrast.

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