update_vehicle

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

Discloses it updates fields and mentions 'updated record' but does not specify partial vs full update, error behavior, or permissions. With no annotations, more detail would improve transparency.

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?

Very concise, well-structured with sections (use when, example, common fields). No unnecessary words, front-loaded with main action.

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?

Despite output schema existing, description lacks crucial details about the 'fields' parameter and return value. Incomplete for an update tool with a complex parameter.

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%. Description lists common fields but does not explain the structure of the 'fields' parameter (object keys, required vs optional). Example implies flat parameters, conflicting with schema.

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?

Description clearly states 'Update one or more fields on an existing vehicle listing' with specific verb and resource. Differentiates from siblings (create, delete) and provides concrete examples.

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?

Includes 'Use when' with natural language examples, indicating when to use. No explicit exclusions or alternatives, but context is clear given sibling tools.

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