close_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 is beyond the schema. However, with no annotations, it does not disclose other behavioral aspects such as retry semantics (max_attempts) or completion behavior (wait_for_completion), which are present in the schema.

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?

One concise sentence, front-loaded with the action, no unnecessary words. Perfect size.

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 command tool with optional parameters and no output schema, the description covers the essential purpose and key auto-wake behavior. It could mention the retry/wait behaviors but they are documented in the schema.

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 100%, so each parameter (vin, max_attempts, wait_for_completion) is already described in the schema. The description adds no additional parameter semantics.

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 explicitly states 'Closes the sunroof' with a clear verb and resource, and the em dash adds the auto-wake behavior. It distinguishes from siblings like vent_sunroof and close_windows.

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 explicit when-to-use or alternative guidance is provided; the usage is implied from the action. Siblings like vent_sunroof exist, but there is no note on when to choose close_sunroof over vent_sunroof.

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