tesla_set_temp

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

No annotations provided, and description only states it sets temperature. Does not disclose what happens if climate is off, whether it requires permissions, or any 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?

Extremely concise single sentence with no unnecessary words. Information is front-loaded.

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?

Has output schema so return values are covered, but missing behavioral context like prerequisites and side effects. Adequate for a simple one-param setter but minimal.

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 provides full description of temp_f parameter (including reasonable range). Description adds only 'Both driver and passenger', which is not parameter-specific. Baseline 3 for high schema coverage.

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?

Clearly states the action 'Set cabin temperature target' with unit (Fahrenheit) and scope (both driver and passenger). Distinguishes from sibling climate tools that only turn on/off.

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 guidance on when to use this tool versus alternatives like tesla_climate_on. Does not mention prerequisites (e.g., climate must be on) or context where it would be ineffective.

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