attributes_list_fields

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

No annotations provided. The description implies it's a read-only, lightweight operation but doesn't explicitly state non-destructiveness or error conditions. However, for a simple listing tool, this is adequate.

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?

Two concise, front-loaded sentences. No wasted words; every sentence adds value.

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 there is an output schema (not shown), the description covers the essential purpose and what fields are returned. With only one parameter, it is complete enough for an AI agent to use.

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 coverage is 0% and the description does not add any meaning to the layer_id parameter (e.g., format, source, or validation). The description should clarify what layer_id expects.

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 a vector layer's fields (name, type, length, precision). Differentiates from sibling get_layer_schema by noting it's lighter-weight and doesn't include distinct values or ranges.

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?

Explicitly tells when to use (when you don't need distinct values/numeric ranges) and directly names the alternative tool (get_layer_schema) for when you do need more detail.

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