add_circle_member

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

Beyond the annotations, the description discloses the permission requirement, the side effect of adding a member, the return value shape, and the conditional behavior where status becomes 'Invited' when the circle has the INVITE config flag. This gives the agent important behavioral expectations that annotations alone do not provide.

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 front-loaded with the core purpose and then organized into concise Args and Returns sections. Every sentence adds necessary information; there is no filler or redundant expansion beyond the schema.

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?

The description covers the operation, permission, parameters, and return behavior comprehensively. The only notable gap is that member_type includes 'contact' but the user_id interpretation for that type is not explained, unlike user, group, mail, and circle.

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?

The input schema provides no parameter descriptions (0% coverage), so the description carries full responsibility. It explains circle_id, how user_id is interpreted for each member_type value, the default of 'user', and the full enum of member_type options. This is exemplary parameter documentation.

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 action: adding a user, group, email, or nested circle as a member, which is distinct from sibling operations like remove_circle_member, list_circle_members, and update_circle_member_level. It also names the permission requirement, making the tool's role 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 gives a useful prerequisite ('Requires moderator+') but does not explicitly explain when to choose this tool over alternatives such as join_circle (self-joining) or update_circle_member_level (changing an existing member's role). The usage context is implied rather than stated.

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