sales_detail

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

Annotations are absent, so the description carries full burden. It implies a read operation ('detalle') but does not disclose behavior like return format, pagination, or side effects. No mention of required permissions or data scoping.

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 with no redundancy. It is front-loaded with the core purpose, but its brevity leaves out essential operational details. No waste, though arguably under-specified.

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?

Inadequate for a tool with 3 parameters and no output schema. The description does not clarify expected return values, the role of 'fields' and 'dry_run', or any constraints. An agent cannot reliably invoke this tool correctly based on the information provided.

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 only 33% (only order_id described). The description does not explain the 'fields' or 'dry_run' parameters, which remain undocumented in both schema and description. It merely echoes the order_id UUID concept already present in the schema.

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 states 'Detalle de una orden por UUID' (Order detail by UUID), clearly indicating a read operation for a specific order. This distinguishes it from siblings like sales_list (list of orders) and sales_metrics (aggregated metrics).

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 vs alternatives. The description provides no context on scenarios requiring order details vs list/metrics, nor any selection criteria.

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