aidoo_list_members

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

With no annotations, the description carries the full transparency burden. It discloses the extension mechanism for linked data, which is useful, but does not mention pagination, rate limits, or explicitly state that it is a read-only operation. The term 'list' inherently suggests safety, so it is not misleading.

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 two efficient sentences, front-loaded with the core purpose and followed by a relevant detail about extensions. There is no redundancy or wasted words.

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 list tool with no output schema and no annotations, the description covers the main capabilities: listing all, filtering, and using extensions. It does not explicitly mention pagination or defaults, but the schema's parameter descriptions fill that gap. Overall, it is adequate for agent decision-making.

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 100%, meaning each parameter is already described in the schema. The description adds minimal extra meaning, only clarifying that extensions include linked data like contracts, which aligns with the schema. No additional parameter semantics are provided.

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 explicitly states the tool lists all members or filters by criteria, using the specific verb 'list' and resource 'members'. This distinguishes it clearly from aidoo_get_member (single member) and other list tools for 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 for retrieving member lists and optionally including linked data via extensions, but does not explicitly contrast with aidoo_get_member or other alternatives. It provides context for extensions but lacks clear exclusions or when-not-to-use guidance.

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