get_default_transcription_folder

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

With no annotations provided, the description carries the full burden. It reveals the return value (Documents folder) but lacks details on return format (string path vs object), error conditions (e.g., if Documents is inaccessible), or side effects. For a simple getter, this is adequate but minimal behavioral disclosure.

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 sentences total: purpose declaration, return value specification, and usage guidance. Every sentence earns its place with zero redundancy. Information is front-loaded with the action verb 'Get' and maintains tight focus throughout.

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 the low complexity (simple getter) and lack of output schema, the description adequately compensates by stating what gets returned (Documents folder). It misses explicit safety classification (read-only) and return type format, but is sufficient 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 tool has 0 parameters with 100% schema coverage trivially satisfied. As per rubric guidelines for 0-param tools, this establishes a baseline of 4. No parameter semantics are needed in the description, and none are provided.

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 uses specific verb 'Get' with clear resource 'default folder for saving transcription files' and explicitly states it 'Returns the user's Documents folder.' It distinguishes from sibling 'get_default_export_folder' by specifying 'transcription files' rather than generic exports.

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 explicit guidance 'Call this when the user doesn't specify where to save,' which establishes the trigger condition. However, it doesn't explicitly name alternatives (e.g., using a custom path parameter in transcribe_to_file) or explicitly state when NOT to use it beyond the implication.

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