get_map_infos

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

No annotations are provided, so the description carries the full burden. It discloses that it returns the map tree structure but does not mention any side effects, requirements (e.g., project must be loaded), or limitations. It is minimally transparent but could be improved.

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 16 words. It is very concise and front-loaded with the key action and resource. Every word adds value, making it highly efficient.

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 no parameters and no output schema, the description is mostly complete. It tells what the tool does and what it returns. However, it could mention prerequisites (e.g., a project must be loaded) or elaborate on the tree structure format slightly for full completeness.

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 input schema has zero parameters, so schema coverage is 100%. The description does not need to add parameter semantics beyond what the schema provides. It appropriately describes what the tool does without parameter details.

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 'Get information about all maps in the project (MapInfos.json). Returns the map tree structure.' It specifies the verb 'get', the resource 'all maps', and distinguishes itself from sibling tools like get_map (which gets a single map) by explicitly mentioning 'all maps' and 'tree structure'.

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 implies usage by stating what it returns, but it does not provide explicit guidance on when to use this tool versus alternatives. It lacks statements like 'Use this when you need the overall map hierarchy' or 'Not for individual map data.'

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