rivian_get_vehicle_state

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

No annotations are provided. The description implies a read-only operation by listing status items but does not disclose behavioral traits such as real-time data, authentication needs, or side effects.

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?

A single sentence with a clear verb-object structure. It is front-loaded with 'Check your vehicle's current status' but includes a lengthy list with 'and more' which could be trimmed.

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?

The description lists many status categories but does not specify the output format (e.g., JSON structure). Given no output schema, the description could be more complete about what the returned data looks like.

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?

The schema already describes the 'properties' parameter at 100% coverage. The description adds value by enumerating example property categories (battery, range, doors, etc.), which helps the agent understand what can be queried.

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 clearly states 'Check your vehicle's current status' and lists numerous specific categories like battery, range, doors, etc. It distinguishes from siblings which cover charging, OTA, drivers, etc.

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 implies when to use (to check vehicle status) but does not explicitly exclude scenarios or mention alternatives like rivian_get_ota_status for software updates.

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