Get media folder path

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them by naming the concrete folder ('collection.media') and stressing that the path is on the computer running Anki — a meaningful caveat for a remote client, which would receive the server's filesystem path rather than its own.

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?

A single sentence with zero filler, front-loading the return value and then qualifying it with the folder name and host machine. Every clause 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?

For a zero-parameter, read-only lookup with no output schema, the description carries the necessary burden by explaining exactly what string is returned. Minor gap: it does not say what happens if the media folder has not been created yet, or whether the path uses native separators.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly avoids inventing parameter discussion for a no-argument tool.

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 ('Returns') and an exact resource ('the absolute path of Anki's media folder (collection.media)'), and clarifies the machine context. No sibling tool returns a folder path — the others operate on media file names, contents, or deletion — so the agent can distinguish this without opening any schema.

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?

Usage is implied by the narrow purpose: an agent needs it when constructing or displaying an on-disk path to media assets. There is no explicit when-to-use statement, no mention of alternatives such as get_media_files_names, and no note about prerequisites (e.g., whether the media folder must already exist).

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