scope_wavesource_info

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

No annotations are provided, so the description carries the full burden. It lists the returned fields and implicitly describes a read operation. While it could explicitly state it is non-destructive, the listing of returned values and the prerequisite condition add sufficient transparency.

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 5 sentences, front-loading the purpose. Every sentence adds value (purpose, return fields, model availability, transport). Could be slightly more concise but is well-structured.

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 tool has no parameters and an existing output schema, the description fully covers what the agent needs: purpose, returned fields, prerequisite check, and transport. It is complete for a read-only info tool.

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, making the schema fully descriptive by default. With no parameters, there is nothing to add beyond what the schema conveys, so a baseline of 4 is appropriate.

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 starts with 'Get all current WaveSource generator settings', which is a clear verb+resource. Among siblings like scope_wavesource_configure and scope_wavesource_enable, this tool is distinctly for reading 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?

It states the tool is 'Only available on models with has_wavesource=True' and advises to 'Check scope_capabilities first'. This provides explicit prerequisite guidance, though it does not explicitly list alternatives.

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