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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety and behavior profile. The description adds context about return fields (dates, biography) and purpose but does not reveal new behavioral traits beyond the annotations. No contradiction.

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 concise, conveying the tool's purpose and key use in a single sentence. It is front-loaded with the core action. Minor structural issue with the dash, but overall efficient and clear.

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?

Given the output schema existence and rich annotations, the description adequately covers the tool's function. It explains what the search returns and its cross-referencing purpose. No significant gaps, though pagination or result format could be mentioned.

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 100% with clear descriptions for both parameters (q: artist name, limit: number of results). The description does not add additional meaning to the parameters beyond what the schema provides, aligning with the baseline of 3.

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 the tool searches artists/makers in the Art Institute of Chicago collection, specifies return fields (name, dates, biography), and highlights the primary use case of finding artist IDs for cross-referencing with artwork searches. This distinguishes it from siblings like culture.artic.artwork and culture.artic.search.

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 implies the tool is for finding artist IDs to cross-reference with artwork search, providing clear context for when to use it. However, it does not explicitly state when not to use it or mention alternatives, lacking exclusion criteria.

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