ventas_hoy

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

With no annotations supplied, the description carries the full burden, and it does add real behavioral detail: 'today' is defined as the America/Managua business day, which removes the main ambiguity for an agent. It also signals that the output is phrased in voseo and ready for voice. It stops short of describing what the response contains, such as a single total versus a breakdown, or how an empty day is handled.

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?

A single short sentence that front-loads the core question and then adds the two qualifying details. No filler, no restatement of the tool name beyond what is needed.

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 parameterless, likely read-only lookup with no output schema, the description covers what is returned conceptually and the time boundary that defines it. The only remaining gap is the exact shape of the result, which is a minor omission at this complexity.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The timezone note actually adds context that a parameterless tool might otherwise leave unclear.

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 and resource: 'cuánto vendió el negocio hoy', which tells an agent this returns today's sales total. The time scope is made explicit, which implicitly distinguishes it from ventas_periodo, but that sibling is never named.

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?

Usage is only implied by the word 'hoy'. The description never states when to prefer this over the sibling ventas_periodo, nor does it set exclusions, such as other ranges or per-user filtering.

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