record

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

Discloses auto-stop on silence detection, duration as maximum, and raw WAV return. No annotations provided, so description carries full burden; it covers key behaviors but could mention if recording requires mic permissions.

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?

Concise, front-loaded with purpose, then auto-stop, duration clarification, usage guidance, and explicit args/returns. Every sentence adds value.

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?

Completes all needed context: purpose, behavior, parameter meaning, return type, and comparative guidance. Sufficient for a simple tool with output schema.

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?

Schema lacks parameter description (0% coverage). Description provides meaning: duration is max recording time in seconds, with default 10 and max 120, adding essential context.

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 it records audio from the microphone, auto-stops on silence, and returns a WAV file. It distinguishes from siblings 'converse' and 'practice' by noting they also analyze.

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?

Explicitly advises preferring 'converse' or 'practice' for combined recording and analysis, using 'record' only for raw WAV. Also explains duration as max time not requiring full wait.

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