list_gis_layers

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

No annotations available. The description does not disclose behavioral traits such as read-only nature, permission requirements, or side effects. It merely states the output without explaining behavior beyond the obvious.

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 that front-loads the core purpose. No wasted words, but could be expanded slightly for completeness 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?

Although an output schema exists, the description omits context about input parameters and when to use the tool. With 5 parameters and no guidance, the description is incomplete for effective tool selection and invocation.

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 does not explain any parameters. The five parameters (project_path, open_current_project, timeout_seconds, include_fields, include_data_source_details) are not mentioned, leaving the agent to infer their meaning from titles alone.

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?

Description clearly states the tool lists maps, layers, fields, and spatial references and returns Resource URIs. It provides a specific verb ('list') and resource ('GIS layers'), but does not distinguish from sibling tools like inspect_gdb or inspect_project_context.

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 usage context or guidance provided. The description does not indicate when to use this tool versus alternatives, nor any prerequisites or conditions.

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