Artsy Analytics MCP Server

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It doesn't mention authentication requirements, rate limits, response format, whether data is real-time or cached, or any limitations of the 'comprehensive' overview. The agent must infer behavior from the tool name and description alone.

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 a single, efficient sentence that gets straight to the point. However, it could be more front-loaded with differentiation from siblings, and the phrase 'comprehensive analytics overview' is somewhat redundant with 'all major metrics'.

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 tool with no annotations, no output schema, and 12 sibling tools offering similar analytics, the description is insufficient. It doesn't explain what 'comprehensive' means, what metrics are included, how this differs from query_analytics_custom, or what format the response takes. The agent lacks crucial context for proper tool selection.

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 100%, so the schema already documents both parameters well. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what 'comprehensive analytics' includes or how the period parameter affects the returned metrics.

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 verb 'Get' and resource 'comprehensive analytics overview for a partner', specifying it includes 'all major metrics'. It distinguishes from siblings by implying breadth rather than specific metric categories, but doesn't explicitly name how it differs from tools like 'query_analytics_custom'.

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 on when to use this tool versus the many sibling tools is provided. The description mentions 'comprehensive' and 'all major metrics', but doesn't specify when this broad overview is preferable to the more specific sibling tools like get_partner_sales_stats or get_partner_audience_stats.

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