coda_list_doc_analytics

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

Annotations already declare read-only, idempotent, and open-world. Description adds ownership requirement and data scope (date range, engagement metrics), complementing annotations without contradiction.

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?

Very concise: 4 short sentences, each adding essential info. Purpose in first sentence, metrics in second, restriction in third, alternative in fourth. No wasted 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?

Given full schema coverage, presence of output schema, and comprehensive annotations, the description covers purpose, usage, restrictions, and alternatives. Adequate for 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 coverage is 100%, so description adds minimal value beyond parameter names and types. It implies date-range filtering, but schema already covers that. Baseline 3 appropriate.

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?

Description clearly states it lists analytics data for docs with specific metrics (views, copies, likes, sessions). It distinguishes from sibling tool 'coda_get_doc_analytics_summary' by noting aggregated totals vs per-doc breakdown.

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?

Explicitly states availability only to doc owners and provides a clear alternative for aggregated totals via 'coda_get_doc_analytics_summary', guiding appropriate tool selection.

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