get_messages_bot

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

While annotations already mark the tool as readOnly, the description adds that it returns a metric (volume), not raw messages, and requires a date range. This provides useful behavioral context beyond the annotation's simple read-only label.

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, well-structured sentence that immediately communicates the tool's purpose and scope without any extraneous words. It is optimally concise and informative.

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 the absence of an output schema, the description should clarify the return format (e.g., total count, daily breakdown). It only states 'volumen', which is vague. However, for a simple metric tool with two parameters and no nested objects, it is moderately complete.

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% with clear parameter descriptions. The description reinforces the date range format (YYYY-MM-DD) but adds no new semantic information beyond what the schema already provides, meeting the baseline.

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 'volumen de mensajes enviados por el bot en un rango de fechas', specifying both the verb (metric retrieval) and resource (bot messages). It distinguishes from the sibling 'get_messages' which likely covers all messages, making its purpose unambiguous.

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 implies the tool is for bot message metrics but does not explicitly state when to use it over alternatives like 'get_messages' or other metric tools. No exclusions or scenario guidance is provided.

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