get_paths

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

With no annotations, the description carries the full behavioral burden. 'Resolve' implies a read-only lookup, but it never states that nothing is mutated, whether a missing recordings-settings.json causes an error or a fallback, or whether the resolved path can differ from a default. Only the existence of the custom-settings override is disclosed.

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 front-loaded sentence with no padding. It is efficient, though the trailing clause about recordings-settings.json is dense jargon that could be split for readability without losing brevity.

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?

No output schema exists, so the description must describe the return value, and it only gestures at it ('the actual recordings and Projects directories'). It does not say whether one or two paths come back, in what format, or what happens when the custom settings file is absent.

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 the baseline is 4. There is nothing for the description to disambiguate, and it correctly avoids inventing arguments.

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 ('Resolve') and resource ('recordings and Projects directories'), plus the twist that a custom recordings-settings.json is honored. An agent can tell this is a path/config lookup rather than a media operation, so it is distinguishable from the Zoom-oriented siblings, though the description never names those siblings explicitly.

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 statement of when to call this tool, when not to, or which sibling it substitutes for. The agent must infer that it exists to discover directory locations before invoking file-based siblings, and nothing confirms or denies that inference.

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