get_analytics

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

The description implies read-only behavior (query returning a table) but does not explicitly state it's non-destructive or safe. With no annotations, this is a gap.

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?

Well-structured with Args section and example, but the example is somewhat verbose. Overall concise and easy to read.

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 output schema exists (not shown), return values don't need explanation. Parameters are well-documented. However, limitations like pagination or result size are not mentioned.

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 coverage is 0%, but the description thoroughly explains each parameter including formats, defaults, and acceptable values (e.g., periods accept fixed and relative keywords). This adds significant meaning 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?

The description clearly states the tool runs an aggregate analytics query and returns a readable table, distinguishing it from sibling 'get_analytics_raw' which likely provides raw data.

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 mentions using search_metadata to find UIDs and provides an example, but does not explicitly state when to use this tool vs alternatives like get_analytics_raw or when not to use it.

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