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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results come back as 'canonical links and native app handoffs', which is useful context about the nature of the response, but it says nothing about pagination behavior, rate limits, or result ordering.

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 the purpose front-loaded and no filler. Nothing in the text is repeated or wasted; it is simply short enough that it omits useful detail rather than padding with noise.

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?

An output schema exists, so return-value explanation is not required, and annotations cover the safety profile. The remaining gaps are the absence of any sibling routing (search_artists vs this tool) and any mention of pagination, which is significant for a search endpoint exposing limit/offset.

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 all three parameters (query, limit, offset) are undocumented in the schema. The description partially compensates for 'query' by naming the search axes (title, artist), but limit and offset — including the 50-item cap and pagination semantics — are entirely unaddressed in both places.

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 ('Find'), a named resource ('AB[500] artworks and series'), and the search axes ('by title or artist'). However, the tool is named search_projects while the description talks about artworks and series, and the sibling list contains search_artists and get_artwork without any differentiation of scope, leaving some ambiguity about what a 'project' is here.

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 never says when to reach for this tool instead of search_artists, get_artwork, or get_project, nor any exclusion conditions. Only implicit usage is conveyed by 'Find ... by title or artist'; no routing guidance is offered.

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