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

The annotation readOnlyHint=true already signals a safe read operation. The description adds valuable behavioral details: returns artifacts 'without their content payload,' the meaning of status='' as returning all statuses, the limit default (20) and maximum (100), and that the 'total' field reflects the unfiltered count. These go beyond the annotation and help the agent understand pagination and response semantics.

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 five sentences but every sentence contributes meaningful information: purpose, filtering, limit behavior, total field, and use case. It is front-loaded with the main action and avoids fluff. It could be slightly more concise, but it is well-structured and does not waste 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?

For a low-complexity list tool with only two optional parameters and no output schema, the description is complete. It covers return scope (artifact types, no content), filtering semantics, limit constraints, the total field behavior, and a clear use case. No critical information is missing for an agent to select and invoke this tool 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?

Schema description coverage is 0%, so the description must fully compensate. It does: for 'status' it explains the exact format (e.g. "pending_review") and the special empty string to return all; for 'limit' it provides the default and max, which is not in the schema. This is essential information that adds significant meaning beyond the schema's bare types and defaults.

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 uses a specific verb ('Return') and resource ('artifacts') listing the three kinds (llms_txt, json_ld, defense_nodes) and explicitly excludes content payload. This makes it clear what the tool does and distinguishes it from siblings like get_artifact (which likely returns content) and approve_artifact/activate_artifact (which are actions).

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 gives an explicit use case: 'Use when an agent needs to discover which artifact IDs are available before approving or activating a specific one.' This clearly states when to use it. It does not name alternative tools explicitly, but the mention of 'before approving or activating' implies the appropriate context relative to sibling tools, so it is strong but not a full when-not guidance.

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