list_members

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

Goes well beyond the annotations (readOnly/idempotent/non-destructive are already declared) by disclosing the cost profile ('two requests to Odoo.sh'), the limit bounds (50 default, 200 max), per-field truncation at 256 bytes with a `truncated` flag, and a prompt-injection warning about treating member data as untrusted. Those are exactly the operational facts annotations cannot express.

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?

Purpose is front-loaded and the Returns/Touches/Bounds sections make it scannable. The one weakness is redundancy: the field list in the opening sentence (login, name, role, GitHub user number, pending login) is largely restated in the Returns block.

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?

Covers everything an agent needs for a read-only list call: permissions, request cost, pagination binding, truncation behavior, and a safety note on returned personal data. Return shape is additionally backed by a real output schema, so nothing material is missing.

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 0%, so the description must carry the load, and it does add real meaning: `limit` gets a default and a hard ceiling, and `project` is clarified as the project's name rather than an id. It stops short of stating the exact accepted name format or matching rules, which leaves a small gap for a fully undocumented 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?

States a specific verb+resource ('List the members of a project'), the sort order, and exactly which fields come back, so an agent can distinguish it from list_projects, get_project_overview, and list_audit_log at a glance. It also scopes who sees the data ('an admin of the project only').

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 makes the use case clear (enumerate project membership) and states the admin-privilege precondition, which shapes when the call is viable. It never names an alternative sibling or an explicit 'do not use this when…' rule, so it stops short of full routing guidance.

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