list_circle_members

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description does not need to re-state those. It adds meaningful behavior context by explaining that full_details includes inherited circle memberships and by defining the return fields and their enum meanings.

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, then provides compact Args and Returns sections. The enum lists are detailed but serve a clear purpose for understanding returned values; no sentence is wasted.

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 two-parameter read-only tool, the description fully covers the purpose, parameters, and return shape. The inclusion of exact field names, enum values, and the effect of full_details makes this complete enough for an agent to call confidently without needing additional context.

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 0%, so the description must carry the parameter meaning. It explicitly explains circle_id as a string circle id and full_details as 'If True, include extended info such as circle memberships inherited through this one,' adding real semantics beyond the bare schema properties.

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 opens with 'List all members of a circle,' which names a specific verb and resource. This clearly distinguishes it from sibling tools like list_circles or get_circle, and the return-value details reinforce the purpose.

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 usage context is implied by 'List all members of a circle': an agent would call this when it needs the member list for a known circle. However, there is no explicit when-to-use guidance, no exclusion criteria, and no mention of alternatives such as search_circles or list_circles.

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