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

Annotations already declare readOnly and non-destructive, and the description adds value by stating that only public artifacts are searched and no bearer token is required. That fills the auth/scope gap beyond the safety 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 tightly written sentences; the key operation is front-loaded and the auth note earns its place. There is no filler or redundancy.

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?

With a complete input schema, an output schema, and safety annotations, the description supplies the remaining behavioral essentials (public scope, no auth). A brief pointer to sibling discover_snacks would make it fully complete.

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?

All five parameters are fully documented in the schema, so the baseline is 3. The description maps most filters to prose but adds no new meaning beyond the schema; 'ranking' also loosely refers to the sort parameter.

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 names a specific verb and resource ('Search public artifacts') and lists the exact filter dimensions (words, topic tag, format, ranking), making the tool's job clear. It does not explicitly differentiate from the sibling discover_snacks, so it loses the top point.

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?

Searching public artifacts by words/tag/format/ranking plus the no-bearer-token note gives a clear context for when this tool is appropriate. However, it never names alternatives or says when not to use it, so guidance is implied rather than explicit.

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