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

The readOnlyHint annotation already covers safety, and the description adds meaningful behavioral detail: results are grouped by type, by_type_counts provides the full summary, type matching is synonym-aware ('MCP matches MCPServer'), and include controls body inlining. This goes beyond the annotation without contradicting it.

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 a single dense sentence that front-loads the core purpose before parameter guidance. Every clause adds useful information, though the parenthetical 'by_type_counts is the full summary' and the nested synonym note make it slightly harder to parse at a glance.

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 read-only listing tool with one required parameter, the description covers the essential invocation details: what is returned, how grouping works, how to filter by type, and how to request content. Since there is no output schema, more explicit return-shape detail would help, but the description is sufficient for correct invocation.

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?

With schema description coverage at 50%, the description compensates by explaining the `type` behavior (synonym-aware) and the exact use of `include` with the enum value 'content'. The `aid` parameter is not described in the schema, but 'One API's artifacts' implies its role sufficiently. The `context` parameter is already well described in the schema.

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 a specific resource ('One API's artifacts') and an organizing behavior ('grouped by type'), making the tool distinguishable from broader artifact tools in the sibling list. It does not explicitly name a sibling alternative, but the scope is unambiguous enough for an agent to select it confidently.

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 clear guidance on optional parameters ('pass `type` to scope the list to one type', 'include=["content"] to inline the bodies'), but it does not explicitly say when to use this tool versus siblings like get_provider_artifacts or find_artifacts. Usage context is implied by 'One API's artifacts' rather than stated as a selection rule.

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