teslamate_get_drive_gpx

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

No annotations exist, so the description carries the full burden. It implies a read operation via 'Fetch' but discloses no behavioral traits such as authentication requirements, rate limits, data size, or unsafety. For a tool without annotations, 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 a single, coherent sentence with no waste. It is front-loaded with the key information. However, given the sparsity, one could argue it is under-specified rather than concise, but structurally it's clean.

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?

With no output schema, the description does not explain what the GPX export contains (e.g., raw GPS points, metadata). The tool is simple with two params, but for adequate completeness, at least a note on the response format or typical usage would be expected.

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 0%, and the description adds no meaning beyond the endpoint pattern. 'driveId' and 'userId' are not explained; their types and purposes are left entirely to the schema, which is minimal. For two parameters, this is highly inadequate.

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 action (Fetch), the resource (drive GPX export), and references the API endpoint pattern. It distinguishes this tool from siblings like teslamate_connection_info or teslamate_list_endpoints by being specific to GPX exports for a particular drive.

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 is provided on when to use this tool versus alternatives, nor are there any contextual or prerequisite hints. The description only states what it does, leaving the agent without strategic direction.

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