list_importlist

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds only the HTTP endpoint, which is not behavioral context. It does not disclose return format, pagination, or any side effects, but given the annotations, the bar is lower. However, it adds no meaningful behavioral information beyond the name.

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 extremely concise, consisting of two lines: the purpose and the HTTP endpoint. It is front-loaded with the core action. The endpoint line may be considered unnecessary detail for an agent but is not harmful. It is appropriately sized for a simple list operation.

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 simple with no parameters and an output schema present, so the description doesn't need to explain return values. However, given the large number of sibling tools, it could benefit from explicitly stating that it lists all import lists and differentiating from related tools. As it stands, it is minimal but functional, lacking a bit of context to fully disambiguate.

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?

There are no parameters in the schema, so schema description coverage is trivially 100%. The description does not need to elaborate on parameters. With 0 parameters, the baseline is 4, and the description is adequate for the absence of parameters.

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 states 'Read ImportList.' which clearly identifies the verb (read) and resource (ImportList). The HTTP endpoint adds a concrete reference. It is distinct from siblings like list_importlist_schema and get_importlist_by_id, though it doesn't explicitly name them. The purpose is clear and unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as get_importlist_by_id or list_importlist_schema. It merely restates the operation without offering context on selection criteria or exclusions. There is no mention of how this differs from other list operations.

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