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

With no annotations, the description carries the full behavioral burden. It discloses that results are public and ordered by verification priority plus heat, but says nothing about pagination behavior, total result counts, rate limits, or whether any auth is needed beyond 'public'.

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?

A single dense sentence that front-loads the resource and scope, then the returned fields and ordering. It is efficient with no filler, though cramming scope, fields, and sort into one sentence slightly reduces scannability.

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 simple two-parameter read-only listing with no output schema, the description covers what the tool returns and how results are ordered. It omits result-count and pagination semantics, which an agent would need to page correctly, leaving a gap for a tool with no annotations.

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 both parameters (limit 1-200 default 50, offset default 0) are already documented in the schema. The description adds only the sort order, not parameter-level detail, so the baseline 3 applies.

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 states a specific resource (member directory) and its scope (public, verified one-person-company members), plus the fields returned and sort order. However, it never distinguishes itself from the sibling soloteam_member (singular), so the agent must guess which to call.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only usage signal is the word 'public', which implies browsing rather than filtering, but nothing tells the agent how this differs from soloteam_member or soloteam_match.

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