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 but only states the action ('update') without behavioral details. It doesn't disclose permission requirements, whether changes are reversible, side effects (e.g., on associated photos), or error handling, which are critical for a mutation tool with undocumented parameters.

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, front-loaded sentence: 'Update an album group'. There is no wasted verbiage, making it efficient for quick scanning, though this brevity contributes to gaps in other dimensions.

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 mutation tool with 4 parameters, low schema coverage (25%), no annotations, and no output schema, the description is incomplete. It lacks essential context such as behavioral traits, parameter meanings, and usage guidelines, making it insufficient for safe and effective tool invocation.

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 low at 25%, with only 'group_status' documented. The description adds no parameter semantics beyond the tool name, failing to explain what 'group_id', 'group_name', or 'group_desc' represent or how they affect the update, leaving most parameters inadequately described.

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 'Update an album group' clearly states the action (update) and resource (album group), but it's vague about what an 'album group' represents in this context. It doesn't distinguish this tool from sibling update tools like updatePortfolioPhoto or updateCategory, leaving ambiguity about the specific domain.

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. The description doesn't mention prerequisites (e.g., needing an existing group_id), exclusions, or comparisons to related tools like createPortfolioGroup or deletePortfolioGroup, leaving the agent to infer usage from context alone.

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