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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of prerequisites such as the vehicle needing to be awake, or what error state results from locking an already-locked vehicle.

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 sentence is short, but this is under-specification rather than conciseness — the brevity leaves every meaningful question unanswered.

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?

A state-changing vehicle command with no output schema and an undocumented identifier parameter needs far more: which vehicle is targeted, what preconditions exist, and what happens on failure. None of this is present.

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 coverage is 0% and the single parameter (vin) is unexplained in both schema and description. Notably, vin is not marked required, yet nothing in the description clarifies whether it is optional or how the target vehicle is resolved without it.

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?

"Locks the vehicle" is essentially a restatement of the tool name/title, adding no scope or distinguishing detail. An agent can infer that it is the inverse of unlock_vehicle, but the description itself does no differentiating work.

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 guidance on when to use this tool versus unlock_vehicle or any other sibling, and no preconditions are mentioned. Usage is only implied by the name.

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