analytics_session_timeline

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

With no annotations, the description gives basic behavioral context (read-only, aggregated counts). It does not mention any side effects or special behaviors, but for a simple analytics tool this is minimal but sufficient.

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, concise sentence that communicates the core function. No extraneous words.

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?

While the tool is simple, the description lacks details about the output format, data scope, or any restrictions. For a tool with no output schema, the description should provide more context about what the response contains.

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?

The description does not explain the parameter 'days' beyond implying a time period. The schema has 0% coverage and the description provides no additional semantic meaning for the parameter.

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 provides daily session counts by status over a given period. However, it does not explicitly differentiate from sibling analytics tools like analytics_backend_stats.

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 provides no usage guidelines or context about when to use this tool versus alternatives like analytics_backend_stats or analytics_export.

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