project_list_layers

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

Discloses that feature counts come from provider index, not scanning, which is a behavioral detail. Since no annotations exist, this adds value. Could mention if read-only or performance implications.

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?

Three sentences, first states main action, then lists output fields, then usage guidance. No wasted words.

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 output schema exists, description adequately covers returned fields and behavioral aspects. No missing information for a listing tool.

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?

No parameters exist; input schema is empty. Baseline 4 as per rules since no parameters to document.

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?

Clearly states it lists every layer in the project and details returned fields. Distinguishes from siblings like get_layer_schema and get_layer_sample.

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?

Provides explicit post-use guidance on using the returned id for further layer operations. Does not explicitly state when to use vs alternatives but context implies this is the universal layer listing tool.

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