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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds non-obvious behavioral context: results are valid projectId inputs to specific generation tools, and omitting characterId falls back to the project's mirrored character. It does not disclose ordering, pagination, or default filtering behavior, so it stops short of a 5.

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?

Three sentences, front-loaded with what it does and immediately followed by triggers and the downstream handoff. The trigger list is slightly crammed into one sentence but no sentence is wasted.

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?

For a two-parameter read-only list with no output schema, the description supplies the essential missing piece (what the returned ids are for) and the implicit character fallback. The only real hole is parameter behavior, which is addressed in the parameter dimension.

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% and the description says nothing about either parameter. limit and includeArchived are left entirely to bare schema typing with no guidance on defaults or when to set them, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ("List the user's AIGE work projects") and adds the output contract that matters: it returns valid projectId targets for generation. That distinguishes it from the sibling list tools (antix_list_characters, antix_list_channels) without the agent needing to open a schema.

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?

Gives explicit trigger phrases ("put it in my project", naming a project, wanting output live in the same AIGE workspace) and names the downstream tools that consume the id (image, image-batch, video). This is a clear when-to-use plus how-to-continue chain.

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