vent_sunroof

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

The description discloses the auto-wake behavior ('auto-wakes if asleep'), which adds useful behavioral context. However, with no annotations present, the description carries the full burden and omits details like permission requirements, reversibility, or failure behavior.

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 a single concise sentence that front-loads the action verb and includes an important behavioral note. Every word earns its place with no redundancy.

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 a simple action tool with no output schema and all parameters documented, the description provides the essential purpose and a key behavioral detail. It does not need extensive elaboration, though it could mention edge cases or errors.

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?

All three parameters (vin, max_attempts, wait_for_completion) have descriptions in the schema, so schema coverage is 100%. The description adds no extra parameter-specific meaning, meeting the baseline of 3.

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 uses a specific verb and resource: 'Vents the sunroof'. This clearly distinguishes it from sibling tools like 'close_sunroof' and 'vent_windows' by indicating the exact action and target.

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?

No guidance is provided on when to use this tool versus alternatives such as 'close_sunroof' or 'vent_windows'. There are no prerequisites, context cues, or exclusions mentioned.

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