get_default_transcription_folder

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

No annotations are provided, so the description carries the disclosure burden. It clearly states the return behavior: it returns the user's Documents folder. It does not explicitly state that it creates no files or has no side effects, but for a parameterless getter that returns a known value, the disclosed behavior is adequate.

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 short sentences, each earning its place: the first states the purpose, the second gives the return value, and the third gives the invocation condition. There is no filler or redundant phrasing.

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?

For a zero-parameter, fixed-return-value helper, the description is complete. It names the tool's purpose, the exact returned folder, and the condition under which to call it. No output schema exists, but the return value is fully described.

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 tool has zero parameters, and the schema has no properties. Per the rules, 0 params earns a baseline of 4. The description adds useful purpose context but no parameter semantics are needed.

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 a specific verb and resource: 'Get the default folder for saving transcription files' and explicitly tells the caller what it returns (the user's Documents folder). This clearly distinguishes it from sibling tools like get_default_export_folder by scoping the result to transcription files.

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?

Provides an explicit invocation condition: 'Call this when the user doesn't specify where to save.' This leaves no ambiguity about when the tool should be selected instead of other folder- or transcription-related siblings.

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