gerent365_report_sales

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

With no annotations, the description must carry full behavioral disclosure. It implies a read-only operation via 'Obtiene' but does not mention return format, pagination, permissions, or potential side effects, which are critical for an agent to invoke it safely.

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 concise sentence, front-loaded with the action and resource, with no unnecessary words or repetition of schema 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?

Despite being a simple read tool, the description lacks essential context: no output format, no details on what the report includes, no handling of edge cases, and no mention of whether the range is inclusive. This leaves significant ambiguity for an agent, especially given the absence of an output 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 provides 100% coverage for both parameters with descriptions and format (YYYY-MM-DD), meeting the baseline for parameter semantics. The description's mention of a date range reinforces the schema but adds no additional meaning about parameter relationships or validation.

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 identifies the tool as retrieving the business's sales report for a date range, using the specific verb 'Obtiene' and the resource 'reporte de ventas del negocio'. It distinguishes itself from sibling report tools like gerent365_report_dashboard by focusing on sales, though it doesn't explicitly mention alternatives.

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 is provided on when to use this tool versus other reporting or data retrieval tools. The description simply states the action without context, prerequisites, or exclusions, leaving the agent without clear decision support.

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