brilliant-directories-mcp

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

No annotations are provided, so the description carries full burden. 'List album photos' implies a read-only operation, but it doesn't disclose behavioral traits such as pagination behavior (hinted by parameters but not described), rate limits, authentication needs, or what happens with large datasets. This leaves significant gaps for an agent to understand how the tool behaves beyond basic listing.

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, efficient phrase ('List album photos') with zero wasted words. It's front-loaded and appropriately sized for a basic listing tool, earning full marks for conciseness.

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?

Given no annotations, no output schema, and 7 parameters, the description is incomplete. It lacks details on return values (e.g., structure of photos list), error handling, or how filtering/sorting parameters interact. For a tool with this complexity and missing structured data, 'List album photos' is insufficient to guide an agent effectively.

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%, with all 7 parameters well-documented in the input schema (e.g., 'limit' with default and max, 'page' as cursor). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 'List album photos' clearly states the verb ('List') and resource ('album photos'), providing basic purpose. However, it doesn't specify what kind of album (portfolio album vs. other types) or distinguish it from similar tools like 'getPortfolioPhoto' (singular) or 'searchPortfolioGroups', making it somewhat vague in context.

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 guidance is provided on when to use this tool versus alternatives like 'getPortfolioPhoto' (for a single photo) or 'searchPortfolioGroups' (for searching groups). The description implies listing but doesn't clarify context, prerequisites, or exclusions, leaving usage ambiguous.

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