AutoEQ MCP Server

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

The description adds valuable behavioral context beyond annotations: it discloses the time-consuming nature ('May take a few minutes') which isn't captured in annotations (idempotentHint=true, destructiveHint=false). Annotations already indicate this is a non-destructive, idempotent write operation, but the description enhances this with practical execution time information that helps the agent manage expectations.

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?

Two perfectly efficient sentences: the first states the core action, the second provides crucial behavioral context about execution time. Zero wasted words, front-loaded with the primary purpose, and every sentence earns its place by adding distinct value.

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 has no parameters, comprehensive annotations covering safety and idempotency, and an output schema exists (so return values don't need description), the description provides adequate context. It covers what the tool does and key behavioral aspects (duration), though could potentially mention data sources more specifically or success indicators.

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 0 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does operationally. No parameter information is needed or missing.

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 action ('Pull latest AutoEQ data from GitHub and rebuild the database') with a specific resource ('AutoEQ data'). It distinguishes from siblings by focusing on database synchronization rather than comparison, profiling, ranking, recommendation, search, or targeting operations. However, it doesn't explicitly differentiate from potential similar tools like 'update_database' or 'refresh_cache' that might exist elsewhere.

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 implies usage context ('May take a few minutes') suggesting it's for periodic updates or after new data is available, but provides no explicit guidance on when to use this versus alternatives like manual updates or other sync methods. It doesn't mention prerequisites, frequency recommendations, or when-not-to-use scenarios.

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