voicebox_get_capture_settings

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

With no annotations, the description provides no detail about side effects, permissions, or whether the tool is read-only. It merely reiterates the function name without additional behavioral context.

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 concise sentence that immediately conveys the tool's purpose. No redundant words or information.

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 zero parameters and an existing output schema (which presumably documents return values), the description is sufficient for a simple getter tool. The agent can infer the tool's basic function without ambiguity.

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 no parameters, so schema coverage is 100% with nothing to document. The description's brevity is acceptable, though it could add meaning by listing what settings are retrieved (e.g., format, sample rate). Baseline for 0 params is 4.

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 clearly states 'Get capture (recording) settings', specifying the verb ('Get') and resource ('capture settings'). This distinguishes it from sibling tools like 'voicebox_get_capture' and 'voicebox_update_capture_settings'.

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 guidance is provided on when to use this tool versus alternatives such as 'voicebox_get_capture' or 'voicebox_get_capture_readiness'. The agent must infer its purpose from the name alone.

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