samsara_create_address

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

With no annotations provided, the description bears full burden for behavioral transparency. It does not disclose that latitude and longitude might be required for some use cases or that externalIds is a nested object with unknown structure. There is no mention of idempotency, error behavior, or what happens if the address already exists. The description is too brief to inform an agent about behavioral traits beyond the simple creation action.

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 a single sentence of 10 words, which is highly concise. It front-loads the key action and resource. However, it sacrifices completeness for brevity; one more sentence about parameter usage would improve it without losing conciseness.

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 has 5 parameters (including a nested object), no annotations, and no output schema, the description should explain more about what is required to create an address, what the response contains, and any constraints. The current description is too sparse for an agent to confidently use the tool without guessing about latitude/longitude cooperation or externalIds format.

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 low (20%), meaning only the 'name' parameter has a schema description ('Address name'). The tool description adds 'saved address/location' context but does not explain what latitude/longitude, externalIds, or formattedAddress mean. While the description helps understand the tool's purpose, it does not compensate for the missing parameter documentation. Baseline is 3 due to low coverage, but no additional value beyond the schema's minimal description.

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 it creates a saved address/location in Samsara for reuse in routes. It uses a specific verb ('Create') and resource ('saved address/location'), and the context of 'for reuse in routes' helps distinguish it from sibling tools like samsara_list_addresses or tools about vehicles and routes.

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 does not provide any guidance on when to use this tool versus alternatives like samsara_list_addresses or samsara_create_contact. It does not mention prerequisites (e.g., needing coordinates or a formatted address) or cases where one might skip using this tool. The description is silent on usage context entirely.

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