start_dsp

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

No annotations are provided, so the description must fully disclose behavior. It only states it turns on audio processing and returns a status, but lacks details on side effects, idempotency, or prerequisites for a successful call.

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?

The description is short and front-loaded with the purpose. However, the 'Args' and 'Returns' sections are unnecessary for a tool with no parameters and add no 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?

Given no output schema and no annotations, the description is incomplete. It does not address common concerns like idempotency, consequences of multiple calls, or whether a patch must be loaded first.

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 description mentions an 'ctx' argument not present in the input schema, which is contradictory. Despite 100% schema coverage (empty schema), it adds misleading information rather than clarifying parameters.

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 the tool's action: 'Enable DSP processing in Pure Data.' It uses specific verb ('enable') and resource ('DSP processing'), and distinguishes from the sibling tool 'stop_dsp' by its inverse functionality.

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 implies usage context ('so that sound can be generated or processed') but provides no explicit guidance on when to use it versus not, nor mentions alternatives like 'stop_dsp'.

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