perception_configure_hearing

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

No annotations are provided, so the description must carry the behavioral disclosure burden. 'Add or update' signals an upsert-like mutation, but the description does not explain side effects, persistence behavior, whether an existing configuration is replaced, or what happens if the component does not exist.

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 compact and front-loaded, with a clear first sentence, a useful example, and a KB pointer. It is easy to scan, though the brevity comes at the cost of missing parameter and behavioral detail.

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?

For an 8-parameter tool with no annotations and no schema-level parameter descriptions, this definition is not complete enough. The output schema may cover return values, but the agent still lacks key input semantics, side-effect awareness, and guidance on tool selection.

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%, and the description must compensate by explaining parameters. It only provides an example for blueprint_name and a general 'Hearing sense config' label; it does not clarify hearing_range, detect_enemies, save, dominant, or the other 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 states a specific action ('Add or update') on a specific resource ('Hearing sense config on an AIPerceptionComponent'). It clearly distinguishes this from sibling tools like perception_configure_sight by naming the sense modality.

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 gives no explicit guidance on when to use this tool versus alternatives such as perception_configure_sight or perception_add_component. The example shows a valid call, but there is no when-to-use, prerequisites, or exclusion criteria.

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