get_sale

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get sale details', implying a read-only operation, but does not specify permissions, rate limits, error handling, or what 'details' entail. This leaves significant gaps in understanding the tool's behavior beyond basic function.

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 concise with 'Get sale details', but it is under-specified rather than efficiently informative. It lacks front-loading of critical information, making it too brief to be helpful, though it avoids unnecessary verbosity.

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 no annotations and no output schema, the description is incomplete for a tool that retrieves details. It does not explain what 'details' include, potential return values, or error cases. For a tool with one required parameter and no structured output information, more context is needed to be fully usable.

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 has 100% description coverage, with 'transaction_id' documented as 'Transaction ID'. The description adds no additional meaning beyond this, such as format examples or constraints. Since the schema handles parameter documentation adequately, the baseline score of 3 is appropriate.

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 'Get sale details' restates the tool name 'get_sale' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'sale details', but lacks specificity about what details are retrieved or how it differs from sibling tools like 'list_sales', resulting in a vague purpose.

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 alternatives such as 'list_sales' or other siblings. The description does not mention prerequisites, context, or exclusions, leaving the agent without direction on appropriate usage scenarios.

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