wwise_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, does not mention side effects, permissions, rate limits, or whether WAQL executes arbitrary commands, leaving the agent to infer safety.

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 stated first and parameter notes following. The Args list is efficient, though it could be slightly clearer about the return_fields string encoding.

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?

An output schema exists, so return values need not be described. However, for a two-parameter query tool with no annotations and 0% schema coverage, the description should at least state that the operation is read-only and clarify how return_fields is encoded. Those gaps leave the definition incomplete.

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 description coverage is 0%, so the description must compensate. It gives a helpful WAQL example and describes return_fields as a JSON array, but it does not explain WAQL grammar sufficiently, nor does it note that return_fields is passed as a JSON-encoded string with a default value.

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 a specific verb and resource: 'Query Wwise objects using WAQL.' This distinguishes it from mutating siblings such as wwise_create_object and wwise_set_property, though it does not explicitly name alternative query tools like execute_waapi or wwise_get_info.

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?

There is no explicit guidance on when to use this tool versus alternatives. The query nature is implied, but the description never states when WAQL querying is appropriate instead of execute_waapi, wwise_get_info, or other sibling tools.

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