search_organization_members

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only says 'search', with no mention of pagination behavior, result format, permission requirements, or any side effects. This is completely inadequate for a 9-parameter tool with no annotations.

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 extremely short (one sentence) and front-loaded, but it lacks substance. It is not verbose, yet every sentence should earn its place; this sentence only states the tool's basic purpose without adding operational value. Thus, it is not 'good conciseness' but rather minimalism.

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 9 parameters daring no output schema, and no annotations, the description only says 'search for organization members'. It does not clarify that this is likely a paginated/search API despite having page, perPage, nextToken parameters, nor does it mention that includeChildren affects scope. The description is wholly insufficient for a complex tool.

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% - all 9 parameters have descriptions in the schema. The description adds no additional parameter semantics, but the baseline of 3 is appropriate given that the schema already explains each parameter like page, query, and includeChildren.

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 'Search for organization members' with a clear verb and resource, but it does not distinguish itself from the sibling tool 'list_organization_members'. Without any scoping or differentiation, an agent cannot tell when to prefer this over the list tool.

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?

No usage guidance is provided. The description does not specify when to use this tool versus list_organization_members, nor does it mention any alternatives or exclusions. This is a critical gap given the sibling list tool.

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