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

The description adds meaningful behavioral context beyond the readOnly and idempotent annotations, notably the precise definition of a dialog ('counts only when the assistant actually replied') and the default date range behavior. This clarifies data semantics and defaults, though it does not describe output format or pagination.

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 two sentences and front-loads the core idea. It lists key metrics and conditions without fluff, making efficient use of words while covering essential 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?

For a read-only analytics tool without an output schema, the description adequately conveys what the return contains (daily series, funnel, top sources, spend) and clarifies edge cases like dialog counting. It is complete enough for an agent to set expectations, though it omits timezone details that are present in the schema.

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 input schema already provides 100% coverage with descriptions for all parameters, including format, timezone, and default behavior. The description repeats the default period in plain language but does not add new semantic 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 what the tool does: it retrieves analytics (dialogs, leads, conversion, response time) for a period, with specific breakdowns like daily series, funnel, top sources, and spend. It distinguishes itself from sibling tools by focusing on analytics metrics rather than single entities or lists.

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 clear context on the tool's purpose and default behavior ('Without from/to the period is the last 7 days'), making it obvious when this tool would be used for analytics reporting. However, it does not explicitly mention when NOT to use it or point to alternative tools like dosai_list_leads or dosai_get_messages.

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