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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds modest behavioral context: the exact-match semantics of the email/name filters and the underlying 'GET /members' endpoint. It says nothing about pagination behavior, ordering guarantees, or result size, which the schema only partially implies via the limit and cursor parameters.

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?

Two compact sentences, no filler, with the tool's scope and its filter set front-loaded before the API endpoint note. Nothing is wasted and the key information arrives first.

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 13-parameter list tool with no output schema and only a minimal readOnly annotation, the definition covers purpose and filters but leaves the return shape (array of members, field set), pagination workflow, and default page size unaddressed in prose. The fully documented schema compensates on parameters, but an agent gets no picture of the response.

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 100%, so the schema already documents all 13 parameters in detail, making 3 the baseline. The description adds a small amount of value by grouping the filters and flagging that email/name are exact matches, but it omits sort, limit, cursor, and is_billing_person entirely, adding no meaning beyond the 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 and resource ('List members (people) of the workspace') and enumerates the filterable dimensions, which is more than a restatement of the title. It does not, however, explicitly distinguish itself from the sibling officernd_get_member (single member) or officernd_list_companies, so an agent must infer the list-vs-get split from naming alone.

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 list of filterable fields implies when the tool is useful (bulk retrieval narrowed by email, status, company, dates), but there is no explicit when-to-use statement, no exclusions, and no routing to alternatives such as officernd_get_member for a single record. Usage is inferable rather than stated.

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