brilliant-directories-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete an album photo' implies a destructive operation, but it doesn't specify whether this action is permanent, reversible, requires specific permissions, or has side effects (e.g., on portfolio groups). This lack of detail is critical for a mutation tool with no safety 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 concise with a single sentence ('Delete an album photo'), which is front-loaded and wastes no words. For a simple tool, this brevity is appropriate, though it may sacrifice completeness.

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 the tool's complexity (a destructive deletion operation), lack of annotations, no output schema, and low schema description coverage (0%), the description is incomplete. It doesn't address behavioral risks, parameter usage, or expected outcomes, making it inadequate for safe and effective tool invocation by an AI agent.

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 has one parameter ('photo_id') with 0% description coverage, meaning the schema provides no semantic context. The description doesn't mention parameters at all, failing to compensate for the schema gap. It doesn't explain what 'photo_id' represents, how to obtain it, or its format, leaving the parameter's meaning unclear.

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 'Delete an album photo' clearly states the verb ('Delete') and resource ('album photo'), providing a basic understanding of the tool's function. However, it doesn't distinguish this tool from its sibling 'deletePortfolioGroup' or other deletion tools in the server, leaving ambiguity about what specifically makes this deletion operation unique.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'deletePortfolioGroup', 'deleteUserPhoto', and 'deletePortfolioPhoto' (this tool), there's no indication of the specific context or prerequisites for deleting an album photo, such as whether it requires authentication or what happens to associated data.

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