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 for behavioral disclosure. 'Create a user photo' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no mention of permissions needed, whether it overwrites existing photos, rate limits, error conditions, or what happens on success. This leaves the agent with critical 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—just three words—with zero wasted verbiage. It's front-loaded with the core action, though this brevity comes at the cost of clarity and completeness. Every word earns its place, but there are too few words to be helpful.

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 complexity (a mutation tool with 4 parameters, 3 required), no annotations, no output schema, and low schema coverage, the description is completely inadequate. It doesn't explain what the tool does beyond the name, provides no behavioral context, and leaves parameters mostly unexplained. This is insufficient for safe and effective use.

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 50% (only 'file' and 'date_added' have descriptions). The tool description adds no parameter information beyond what's in the schema—it doesn't explain what 'user_id' refers to, the meaning of 'type' enum values, or how 'file' should be specified. With low schema coverage and no compensation in the description, parameters remain poorly documented.

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 a user photo' is a tautology that essentially restates the tool name. It specifies the verb 'create' and resource 'user photo', but lacks any detail about what this actually does (e.g., uploads an image file, associates it with a user profile). It doesn't distinguish from siblings like 'createUser' or 'createPortfolioPhoto'.

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. There's no mention of prerequisites (e.g., user must exist), when it's appropriate (e.g., for profile pictures), or what other tools might be related (like 'updateUserPhoto' or 'deleteUserPhoto').

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