get_analytics

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

No annotations provided, so description carries full burden. It discloses the authentication requirement (env var) and the data returned, but does not mention read-only nature, rate limits, or data freshness. Adequate for a simple read tool but not rich.

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 concise sentences, no fluff. First sentence lists the specific analytics returned; second states the prerequisite. Front-loaded with the action and key details.

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 no output schema and 0 parameters, description is somewhat complete but lacks time scope (e.g., all-time vs. last 30 days) and response format. Could be improved with caveats about data aggregation.

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?

Input schema has 0 parameters, so description does not need to explain parameters. Baseline for 0 params is 4. The description adds the environment variable requirement, which is not parameter-related but adds context.

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 retrieves store analytics with specific metrics (total orders, revenue, etc.), using verb 'Get' and resource 'store analytics'. It distinguishes from siblings like list_my_orders (detailed orders) and get_my_store (settings), but does not explicitly contrast them.

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 alternatives (e.g., for detailed order data use list_my_orders). The only guideline is a prerequisite (KARRITO_API_KEY), but no context on when to choose this over other analytics or reporting tools.

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