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

The description explicitly labels the operation as 'Read-only', which is a useful behavioral disclosure, especially since no annotations are provided. However, it does not explain what the required 'id' refers to, what the return shape is, whether any authorization is needed, or whether results are scoped by time.

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 dense sentence with no filler, and the 'Read-only' safety signal is front-loaded. It is concise and well structured, though it sacrifices parameter/return details that other dimensions penalize.

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 tool with no output schema and no annotations, the description should explain enough to invoke it correctly, but it leaves the meaning of the required 'id' ambiguous and does not describe the response format. The listed metric categories provide some value, but critical invocation details are missing.

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 has a single required 'id' property with no description (0% schema_description_coverage), and the tool description does not explain what 'id' represents. The phrase 'for this agent' hints that it may be an agent identifier, but this is not explicit enough for an agent to confidently supply the correct value.

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 uses a specific verb ('Get') and clearly identifies the resource ('Telegram analytics for this agent') plus the metric categories it returns (chats, messages, voice-call duration). This is enough to distinguish it from unrelated tools like crm_stats or get_balance, though it does not explicitly contrast with get_narrator_analytics.

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 phrase 'Telegram analytics' and the listed metric types imply when this tool should be used: when an agent needs read-only Telegram statistics. However, it provides no explicit guidance on when not to use it or which sibling tool might be a better fit for similar analytics needs.

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