rivian_get_charging_schedule

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

Beyond the readOnlyHint annotation it discloses the auth requirement ('requires a signed-in Rivian session and returns an error without one'), the vehicle-selection behavior ('reads the first vehicle on the account'), the output form ('returns readable text'), and confirms no command is sent to the vehicle. This is rich behavioral context an agent could not derive from the annotations alone.

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?

Front-loaded with the returned fields and free of filler. There is mild redundancy between 'It does not change a schedule' and the closing 'Read-only: sends no command to the vehicle', but each targets a slightly different concern, so the cost is small.

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 zero-parameter, no-output-schema read tool, the description covers purpose, fields returned, auth preconditions, error behavior, vehicle scoping, and the sibling alternative. An agent has everything needed to call it correctly.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing parameter-level the description needs to compensate for, and it correctly implies that no arguments are needed.

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?

States a specific verb and resource (get charging schedules saved for the vehicle) and enumerates the exact fields returned (start/end time, duration, enabled, amperage, days of week, location). It explicitly distinguishes itself from the sibling rivian_get_charging_session, so an agent can route without opening schemas.

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?

Gives the use case ('see when the vehicle is set to charge'), an explicit exclusion ('does not change a schedule'), and names the alternative for the adjacent case ('For a charge in progress use rivian_get_charging_session'). Nothing is left to inference.

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