ReftrixMCP

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

Annotations already declare read-only/idempotent safety. Description adds valuable content context (OKLCH color values, gradient definitions) but omits behavioral details about gradient auto-generation logic, pagination for list results, or how brand_name partial matching behaves.

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?

Three sentences with zero waste. Front-loaded with action verb, followed by usage pattern, then content specifics. Each sentence earns its place with no redundancy.

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?

Adequate for basic retrieval but underserves the tool's complexity. With 6 parameters including nested gradient configuration objects, the description should highlight the auto-generation capabilities and search functionality more explicitly. No output schema exists, increasing the description's burden.

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?

With 100% schema coverage, baseline is 3. Description adds the 'no params for list' usage pattern which clarifies the optional ID behavior, but does not explain relationships between parameters (e.g., that gradient_options requires auto_generate_gradients) or add semantic context beyond the schema.

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?

States specific action ('Get') and resource ('brand palette') clearly. Explains the dual-mode behavior (ID for details vs no params for list) effectively. Distinguishes from design/search siblings implicitly through resource specificity, though explicit differentiation is absent.

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?

Provides clear guidance on the primary list-vs-detail usage pattern ('Specify ID for details or no params for list'). However, offers no guidance on when to use brand_name search, mode filtering, or the complex auto-generate gradient features versus standard retrieval.

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