list_importlist_schema

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the endpoint path and the word 'Read', which confirms the read-only nature. It does not add behavioral context beyond the annotations, such as what the schema contains or whether it requires authentication, but it does not contradict the annotations either.

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: two lines, one sentence plus the endpoint. It is front-loaded with the action and resource. It could arguably be slightly more descriptive, but for a zero-parameter read-only schema endpoint, this is appropriately sized and not verbose.

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 the tool's simplicity (zero parameters, read-only, output schema present), the description is nearly complete. The output schema exists, so return values are documented elsewhere. The only minor gap is that it doesn't explain what an 'ImportList schema' is or how it differs from list_importlist, but the endpoint and sibling names provide enough context for an agent to select 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?

The tool has zero parameters, so there is no parameter semantics burden. The description correctly indicates a simple read operation with no inputs. The schema coverage is 100% (vacuously), and the description adds the endpoint context, which is sufficient.

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 'Read ImportList' clearly states the operation (read) and the resource (ImportList), and the endpoint GET /api/v3/importlist/schema reinforces that this is a schema-listing operation. It is distinguishable from siblings like list_importlist (which likely lists actual import lists) and create_importlist (which creates one), though it doesn't explicitly name those alternatives.

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 implies usage: call this to read the ImportList schema. It does not explicitly state when to use this versus list_importlist or create_importlist, nor does it mention that this is a read-only schema endpoint. The endpoint path provides some context, but no explicit when/when-not guidance is given.

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