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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that results are ready-to-use artifacts returned as titles, descriptions and links, which is useful since there is no output schema, but it says nothing about result counts, pagination, or search breadth.

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 tight sentences with zero filler: the first states what is searched and by what input, the second states what comes back. Purpose and result are front-loaded in that order.

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 two-parameter read-only search with full schema coverage and no output schema, the description covers purpose, input mode, and return shape adequately. Gaps are minor: no mention of result limits/pagination or how the optional community parameter narrows a search.

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 coverage is 100%, so both parameters are fully documented in the schema itself; the description only restates the keyword input ('by keywords') and never addresses the optional community parameter. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb+resource ('Search ArtiGram for ... artifacts') and clarifies the artifact domain with examples (calculators, tools, games, dashboards). It is clearly distinguishable from the mutation siblings post_artifact/update_artifact, though it never names an alternative explicitly.

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?

Usage is implied by 'by keywords' and 'ready-made ... use right away', which signals discovery of existing artifacts rather than creation. However, there is no explicit when-to-use statement, no conditions or exclusions, and no routing guidance relative to list_communities or the write siblings.

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