analyze

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Complete audio analysis' gives no information about what the tool actually does, what it returns, whether it's read-only or destructive, what permissions are needed, or any performance characteristics. This is completely inadequate for a tool with no annotation coverage.

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?

While the description is brief, it's under-specified rather than appropriately concise. 'Complete audio analysis' is vague and doesn't provide enough information to be useful. The single sentence fails to earn its place by not conveying meaningful information about the tool's function.

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 complexity implied by 'Complete audio analysis' and the absence of both annotations and an output schema, the description is completely inadequate. It doesn't explain what the tool returns, what 'complete' analysis entails, or how it differs from other analysis tools in the sibling list. This leaves the agent with insufficient information to use the tool effectively.

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 description coverage, so the schema fully documents the absence of parameters. The description doesn't need to explain parameters, and it doesn't contradict the empty schema. A baseline of 4 is appropriate for a zero-parameter tool where the schema provides complete coverage.

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 'Complete audio analysis' restates the tool name 'analyze' in a slightly expanded form, making it tautological rather than providing specific meaning. It doesn't specify what type of analysis is performed or what resources are involved, nor does it differentiate from sibling tools like 'analyze_rhythm' or 'analyze_spectrum'.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools performing various types of analysis (rhythm, spectrum, pattern analysis via AI tools), there's no indication of what makes 'analyze' distinct or when it should be preferred over more specific analysis tools.

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