get_period_stats

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

No annotations provided, so the description must carry the burden of behavioral context. It only states what the tool returns but not how it behaves (e.g., data freshness, pagination, rate limits, or handling of missing data). Minimal disclosure.

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 (one sentence), but includes a distracting '[query]' placeholder. Front-loaded with purpose, but lacks structure (e.g., no separation of input/output). Could be improved with clearer formatting.

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 4 parameters, the description is too brief. It does not explain the return format or how parameters affect results. For a stats tool with many siblings, more detail is needed for complete understanding.

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 75% with descriptions for date, days, and phone. The description adds no extra meaning beyond schema. Period has an enum but no description in schema; description does not clarify its role. Baseline of 3 is 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 provides 'Statistics by period' with 'daily evolution of conversations and messages'. This identifies the verb (get) and resource (period stats). However, it does not differentiate from sibling tools like get_conversation_analytics or get_analytics, which may overlap.

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., get_analytics, get_conversation_analytics). No mention of prerequisites or context for use. The description is purely declarative.

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