List Pixmax models

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

With no annotations, the description carries the full burden. It discloses that the tool returns a list with cost and capacity, and when model is specified, returns prompting guidance. However, it does not mention pagination, rate limits, or authentication requirements. For a read-only list tool, this is adequate but not exhaustive.

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 three sentences, each with a clear purpose: main function, usage guidance, and alternate mode. It is front-loaded with the primary action, and no extraneous information is present.

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 no output schema, the description does a good job explaining the content of the list (type, cost, capacity) and the alternative output for model parameter. It could be slightly more complete by noting the output format (e.g., list of objects), but the core information is present.

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 100% and the description essentially restates what the schema says for both parameters. For model, it repeats 'returns that one model's full prompting + reference guide instead of the list' which is already in the schema. No new semantic information is added beyond the structured definitions.

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 clearly states the tool lists models with type, credit cost, and reference capacity. It also explains the dual behavior when model parameter is given, returning full prompting guidance. This distinguishes it from sibling generation tools by positioning it as the first call to discover model codes.

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 explicitly says 'Call this first to discover exact model codes' and later 'Pass `model` to get one model's full prompting + reference guidance ... before generating.' This provides clear when-to-use guidance and implies it should precede generation tools.

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