samsara_create_route

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the creation action and address requirements, but omits critical details like required permissions, side effects, error conditions, or what happens on success. For a mutation tool, this is insufficient.

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 description is extremely concise at two sentences, with the core purpose front-loaded and an important note following immediately. No wasted words.

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?

Given the tool's complexity (nested stops object, 6 parameters, no output schema), the description is adequate but not complete. It covers core usage but lacks behavioral context (e.g., return value, error handling, permission requirements). The rich schema descriptions help compensate, but gaps remain.

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 description coverage is 100%, so the baseline is 3. The description adds some context (address can be lat/long or formattedAddress, optional times), but mostly reinforces what is already in the schema. It does not independently document any parameters not covered in the 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?

The description clearly states the tool's action ('Create a new route with stops') using a specific verb and resource. It is easily distinguished from sibling route tools like samsara_list_routes, samsara_update_route, and samsara_delete_route, as it uniquely focuses on creation.

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 gives important usage tips (use externalIds for TMS, address requirements) but does not explicitly specify when to use this tool vs alternatives (e.g., when to create vs update, or prerequisites like having drivers/vehicles already). Guidance is present but not exclusionary.

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