brilliant-directories-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create an album photo' without mentioning whether this is a write operation, what permissions are required, how errors are handled, or what the expected output might be. This leaves critical behavioral traits completely undocumented.

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 at just three words, with no wasted language. However, this conciseness comes at the cost of being severely under-specified rather than efficiently informative.

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 tool with 5 parameters (2 required), 0% schema description coverage, no annotations, and no output schema, the description 'Create an album photo' is completely inadequate. It provides no context about the tool's behavior, parameters, or relationship to sibling tools, leaving the agent with insufficient information to use 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?

Schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description provides no information about what 'user_id', 'group_id', 'title', 'original_image_url', or 'status' mean, their expected formats, or how they affect the creation process. The description fails to compensate for the complete lack of schema documentation.

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 'Create an album photo' restates the tool name 'createPortfolioPhoto' with minimal variation, making it tautological. It doesn't specify what 'album photo' means in this context or how it differs from sibling tools like 'createUserPhoto' or 'createPortfolioGroup'.

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 'createUserPhoto' or 'createPortfolioGroup'. The description offers no context about prerequisites, dependencies, or appropriate scenarios for invoking this tool.

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