list_robot_maps

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

Without annotations, the description tells it's a read-side operation (fetch) and describes return format. But it lacks details on permissions, rate limits, or side effects, which are expected for a complete behavioral disclosure.

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 reasonably concise with front-loaded purpose and structured args/returns. The URL reference adds some extra length but provides useful context.

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 simple tool with one parameter and no output schema, the description sufficiently covers the return format and usage context. It does not compare to siblings but is adequate for the task.

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 description adds meaning beyond the input schema by specifying the parameter's role and providing an example value ('GS008-0180-C7P-0000'), which compensates for the 0% 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?

The description clearly states 'Fetches the list of maps associated with a specific robot,' using a specific verb and resource. It distinguishes from sibling tools like download_robot_map_v1 by focusing on listing.

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 notes the HTTP method (POST) and explains the parameter format, providing clear context. However, it does not explicitly state when to use this tool versus alternatives like upload or download.

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