POST /sale (Sale)

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

Annotations indicate this is a mutable but non-destructive operation. However, the description adds no additional behavioral context beyond creation; it omits what the response contains, authentication requirements, or potential side effects. Without an output schema, agents receive insufficient behavioral information.

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 sentence followed by a clear bulleted list. It is front-loaded with the purpose and then efficiently covers each parameter. Every line is necessary and concise.

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?

The description adequately covers all parameters but lacks important context: no mention of the HTTP method (though title hints POST), no response format, no error conditions, and no permissions or prerequisites. For a creation tool with no output schema, this leaves agents with missing information for correct invocation.

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 is minimal (only a body object with no properties), so the description carries the full burden of parameter documentation. It lists all 8 fields with types, required status, and meaningful descriptions (e.g., 'Deve ser um valor maior que zero' for quantity). This adds significant value beyond 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?

The description explicitly states 'Criação de uma venda avulsa', clearly indicating a one-time sale creation. It distinguishes from sibling tools like create_recurring_sale and create_product by specifying the resource and the 'avulsa' (one-off) nature.

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 when to use this tool (for one-off sales) via the word 'avulsa', but does not explicitly state when not to use it or provide direct alternatives. Agents may infer from sibling names, but no explicit guidance is given.

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