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

No annotations are provided, so the description carries the full burden. It discloses that results are grouped by type with counts, that unfiltered results can be large (suggesting performance considerations), and mentions a by_type_counts summary field. It does not describe side effects or authentication, but as a read-only listing, that is acceptable. No contradiction with annotations.

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 sentences with no filler. The opening sentence is front-loaded with the core purpose and artifact categories. The second sentence delivers actionable usage guidance. Everything earns its place.

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 listing tool with no output schema and no annotations, the description covers the essential context: what is returned, how to filter, and the size caveat. It could explicitly state the response shape (e.g., that by_type_counts is a property) but the implication is sufficient for correct invocation. It is complete enough for an agent to use effectively.

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?

The schema covers type and context with descriptions, and slug is obvious as the provider identifier. The description adds value beyond the schema by explaining why filtering by type matters (size) and that by_type_counts serves as the full summary. It compensates for the missing slug description and the 67% schema coverage.

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 what the tool returns: every artifact a provider publishes, grouped by type with counts, and it enumerates the artifact categories (MCP, security, etc.). This is a specific verb+resource and distinguishes it from sibling get_api_artifacts by scope (provider vs API). No ambiguity.

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?

Provides concrete usage guidance: pass 'type' to scope the artifacts list and warns that an unfiltered provider can be 250+ entries. It also explains that by_type_counts is the summary. However, it does not explicitly compare to alternatives like get_api_artifacts or mention when to prefer this over other find_* tools, so the differentiation is implicit rather than explicit.

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