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

Annotations already declare readOnlyHint=true, and the description adds meaningful context: the directory is curated, it supports filtering, and results include portfolio highlights and profile URLs. No contradiction with annotations exists. It could go deeper on sorting or empty-result behavior, but the read-only nature and result contents are sufficiently transparent.

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 two compact sentences with no filler. The first sentence leads with the verb and resource, and the second sentence covers return value and use case. Every phrase 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?

The description is mostly complete: it states scope, filters, return contents, and an intended use case, and an output schema exists so return details are covered. However, the mismatch between 'in Europe' and a region parameter that only accepts Dutch provinces/cities is a meaningful gap. An agent could use this tool for a Berlin muralist request and get nothing because the actual data scope is narrower than described.

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 already documents all four parameters with 100% coverage, so the baseline is 3. The description reinforces the idea of filtering by city/region and style, which maps to the region and style parameters, but adds no new detail beyond the schema. It stays at baseline rather than being elevated.

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?

Clearly states the tool searches a curated directory of muralists and street artists, and uses example styles to define scope. It differentiates itself from the sibling get_muralist_profile by emphasizing directory search rather than individual profiles. However, the geographic scope is slightly overstated: 'Europe' conflicts with the schema's Dutch-only region parameter.

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?

Gives an explicit use case: 'Use this when someone wants to find, hire, or commission a mural artist.' This gives clear context for when to invoke the tool. No exclusions or alternative routing to siblings are mentioned, and the Netherlands-only limitation is not called out.

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