Get Analytics

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

No annotations are provided, so the description carries the full burden. It discloses date format requirements, lists available metrics and dimensions, and notes the 1:1 index correspondence in the response. It does not mention authentication or rate limits, but these are not critical for a read-only analytics tool.

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 concise yet comprehensive: a clear purpose sentence, example questions, enumerated lists of options, date format note, and response structure note. Every sentence earns its place without 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?

The tool has 8 parameters (4 required) and no output schema. The description covers the main functionality, response format, and parameter options well. It could mention sorting/pagination defaults, but these are documented in the schema. Overall it is thorough.

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%, but the description adds value by enumerating and contextualizing metrics and dimensions (e.g., explaining 'hits_view_search' as search impressions) and specifying date format. This goes beyond the schema's enum lists.

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 'Get sales analytics for a date range' and provides specific example questions (e.g., 'show revenue for last week', 'top 10 products by orders'). It distinguishes this tool from sibling tools which are mostly CRUD operations on products/orders/warehouses, making the analytics purpose unique.

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 tells when to use it: 'use it to answer questions like ...' and implies it is for analytics queries. It does not explicitly exclude scenarios or mention alternatives, but the context is clear given the sibling tools.

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