brandsystem-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 describes the tool's output (summary stats and individual items) and hints at its read-only nature by focusing on review and analysis, but lacks details on permissions, rate limits, or response format. It adds some context (e.g., filtering capabilities) but does not fully compensate for the absence of 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 efficiently structured in three sentences: the first states the purpose, the second provides usage guidelines, and the third mentions filtering options. Each sentence adds value without redundancy, making it front-loaded and appropriately sized for the tool's complexity.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers purpose and usage well but lacks details on behavioral aspects like response format or error handling. Without annotations or output schema, more context on what the review output entails would improve completeness.

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 100% description coverage, clearly documenting both parameters with enums and defaults. The description mentions filtering by category or status, aligning with the schema but not adding significant meaning beyond it. Since schema coverage is high, the baseline score of 3 is appropriate, as the description does not enhance parameter understanding.

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 clearly states the tool's purpose with specific verbs ('review', 'shows') and resources ('agent feedback filed via brand_feedback'), distinguishing it from siblings like brand_feedback (likely for submitting feedback) and brand_feedback_triage (likely for triaging individual items). It explicitly mentions summary stats and individual items, providing a comprehensive view.

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 clear context on when to use the tool ('to triage feedback, spot patterns, and prioritize fixes'), which helps differentiate it from other feedback-related tools. However, it does not explicitly state when not to use it or name specific alternatives among siblings, such as brand_feedback_triage, leaving some ambiguity.

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