air_list_artifacts

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

Adds permission requirement 'Requires projects:read' beyond annotations, which already indicate safe read. No contradiction; annotation support is adequate.

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?

Two concise sentences, front-loaded with action, no wasted words.

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?

No output schema, and description doesn't mention pagination, limits, or artifact structure. Provides usage hint but lacks parameter details.

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 has 0% description coverage, and the tool description does not explain what projectPid or includeArchived mean. Agent must infer from names. Description should compensate but fails.

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?

Clearly states 'List document-derived artifacts for a project' with specific verb and resource. However, doesn't differentiate from sibling tools like air_list_documents or air_get_artifact_text.

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?

Mentions using artifact pids in air_start_assessment, providing downstream context, but does not specify when to use this tool instead of alternatives or any exclusions.

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