transcribe_file

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

Goes beyond annotations by disclosing that this operation triggers a purchase/upload, requires a specific file mode and directory, and must not be used with paths outside that directory. It is consistent with readOnlyHint=false and does not contradict any annotation.

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?

Three dense sentences with no filler. Purpose, limits, security constraints, and the path warning are all front-loaded and each sentence earns its place.

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?

Covers purpose, file constraints, and purchase trigger well, and the output schema likely covers return values. However, the purchase workflow parameters are poorly explained, leaving an agent uncertain how to properly supply purchase_id and confirm_purchase.

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 description coverage is 0%, so the description must compensate. It richly documents filename constraints, but says nothing about how purchase_id originates or that confirm_purchase must be true to execute the purchase; language is also undocumented. The 'explicit purchase' line only weakly covers confirm_purchase.

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?

States the exact action ('Buy transcription') and resource ('caller-provided audio file') with size/duration limits. It does not explicitly name sibling alternatives, but the buy-transcription scope is clearly distinct from catalogue, quote, payment_status, and budget_status.

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?

Gives clear operating conditions: the file must be within an owner-configured directory, mode 0600, and uploaded only for an explicit purchase. It does not explicitly route to alternatives or describe the purchase workflow, but the context is sufficient for basic selection.

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