superset_annotation_list

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

With no annotations provided, the description carries the full burden. It discloses key behavior: page numbering starts at 0, page_size max 100, and get_all fetches all records ignoring page/page_size. This goes beyond the schema, which only has type/default. It doesn't cover error handling or return format, but output schema covers that.

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 compact docstring with an Args section. Each sentence provides distinct, necessary information with no filler. It is front-loaded with the one-line summary.

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?

The tool is a straightforward list operation with an output schema present. The description covers all parameters and the pagination behavior, and references the layer list for IDs. No critical gaps for an agent to invoke it correctly.

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%, so the description must compensate. It explains all four parameters with useful semantics: the source of annotation_layer_id, page starting at 0, page_size max 100, and get_all ignoring pagination. This adds meaning beyond the schema's bare types and defaults.

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 uses the specific verb 'List' and resource 'annotations' with a clear scope: 'in the specified layer'. This distinguishes it from sibling tools like superset_annotation_get (single annotation) and superset_annotation_layer_list (layers).

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?

It states 'annotation_layer_id (from annotation_layer_list)', which tells the agent where to obtain a needed prerequisite. It also explains the get_all option versus pagination, clarifying when to use which. However, it does not explicitly name alternatives like 'use superset_annotation_get to fetch a single annotation'.

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