brilliant-directories-mcp

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

With no annotations provided, the description carries full burden. It discloses pagination behavior ('paginated list') and filtering/sorting capabilities, which is valuable. However, it doesn't mention rate limits, authentication requirements, error conditions, or what the response structure looks like (especially important without an output schema). The description adds basic behavioral context but leaves significant gaps.

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 concise with just two clauses: 'List members/users — Get a paginated list of all members.' and 'Supports filtering by any user field and sorting.' Every word earns its place, front-loading the core purpose and efficiently adding key capabilities. No wasted words or redundant information.

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 list/read tool with 7 parameters, 100% schema coverage, but no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and capabilities but lacks important contextual information about authentication, rate limits, error handling, and response format. The schema handles parameter documentation well, but the description doesn't compensate for the missing behavioral context that annotations or output schema would provide.

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 7 parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'filtering by any user field and sorting' which aligns with parameters like property, property_value, property_operator, order_column, and order_type. However, it doesn't provide additional syntax examples or clarify relationships between parameters beyond what's in the schema descriptions.

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 the action ('List members/users') and resource ('all members'), with the verb 'Get' reinforcing the retrieval purpose. It distinguishes from siblings like 'getUser' (singular retrieval) and 'searchUsers' (search vs. list), but doesn't explicitly contrast with 'listUserMeta' or 'listUserPhotos' which list related resources rather than users themselves.

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 implies usage for retrieving paginated lists with filtering/sorting capabilities, but doesn't explicitly state when to use this tool versus alternatives like 'searchUsers' or 'getUser'. It mentions 'Supports filtering by any user field and sorting' which provides some context, but lacks clear guidance on prerequisites or exclusions.

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