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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 'all members of a company' scope, but does not disclose pagination, potential rate limits, auth expectations, or any behavior beyond the listing itself; the annotation coverage makes this acceptable but not strong.

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 a single sentence with no fluff and its core purpose appears immediately. It does partially restate the tool name by beginning with 'GetListCompanyMembers', which is redundant, but the substantive phrase 'lists all members of a company' earns its place.

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 read-only listing tool with one required parameter, a well-covered schema, an output schema, and safe annotations, this is reasonably complete. It would benefit from noting behavioral details like member types or pagination, but the available structured context covers enough for an agent to invoke it correctly.

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?

The input schema already has complete description coverage for the single required companyId parameter, so the schema handles parameter meaning. The description adds no parameter-specific detail beyond implying that the companyId identifies the company whose members should be listed.

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 that the tool lists all members of a company, using a specific verb and a clear resource. It distinguishes the tool from close siblings like company_get_company and company_get_list_companies by centering on 'members', though it does not explicitly name or contrast any sibling.

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?

Usage context is only implied: an agent can infer this tool should be used when it needs the full membership list for a company, but there is no explicit when-to-use or when-not-to-use guidance. There is no mention of alternatives or exclusions, so the agent must rely on the tool name and purpose alone.

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