add_members

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a write operation (implied by 'Add'), specifies it's asynchronous (requiring polling), and provides operational context about tracking with 'guid'. It doesn't cover permissions, rate limits, or error handling, but offers substantial behavioral insight beyond basic purpose.

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 appropriately sized and front-loaded with the core purpose in the first sentence, followed by parameter details. Every sentence earns its place, though the parameter documentation is somewhat dense. It could be slightly more structured but remains efficient.

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 mutation tool with no annotations and no output schema, the description does well by covering purpose, async behavior, polling instructions, and detailed parameter semantics. It lacks explicit error handling, permissions, or return value details, but given the context, it provides substantial completeness for effective use.

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?

Given 0% schema description coverage, the description fully compensates by detailing both parameters. It explains 'group_id' as 'The ID of the group' and provides comprehensive documentation for 'members', including required fields ('nickname' and at least one identifier), optional 'guid', and format specifics. This adds significant meaning beyond the bare 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 specific action ('Add one or more members') and target resource ('to a group'), distinguishing it from sibling tools like 'remove_member' or 'update_membership'. It provides a complete verb+resource+scope statement that is unambiguous.

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 explicitly mentions that this is an 'Async operation' and instructs to 'poll with get_member_results', providing clear context about when to use this tool versus alternatives for checking results. However, it doesn't explicitly state when not to use it or compare it directly to other sibling tools like 'update_membership'.

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