list_members

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

No annotations are provided, so the description carries the full burden. It only states 'list or search' and gives examples, but does not disclose pagination behavior, default return size, or any safety/mutation characteristics. The agent gains minimal behavioral insight.

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 concise: one sentence plus two relevant examples. It efficiently conveys purpose and usage patterns with no wasted words. However, it could be slightly improved by front-loading a brief parameter explanation.

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?

With 4 parameters, 0% schema coverage, and an output schema, the description is insufficient. It lacks explanation of pagination, default behaviors, filter syntax, and offset usage. Despite having an output schema, the description fails to provide a complete understanding for an agent.

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 compensate. The examples illustrate query and filter usage, giving some context for rows and the search string. However, offset is not mentioned at all, and the full semantics of filter values are unclear.

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 'List or search Crossref members (publishers),' which specifies the verb and resource. It distinguishes from sibling tools like get_funder and list_funders, but does not explicitly differentiate from list_funders, so it lacks full sibling differentiation.

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 provides examples but no explicit guidance on when to use this tool vs alternatives. There is no mention of when-not-to-use or context for choosing this over sibling tools like list_funders.

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