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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds no behavioral context beyond that — no note on result ordering, match semantics (substring vs fuzzy), or what an empty result means — so with annotations present a 3 is appropriate.

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 sentences with zero filler: the scope and covered entity types come first, then the filtering mechanic. Every clause earns its place and nothing is repeated from structured fields.

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 five optional parameters all documented in the schema, full annotations, and no output schema, the description covers what an agent needs to invoke the tool. It stops short of describing result shape or match behavior, but that gap is modest given the rich schema.

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%, and the category enum is thoroughly documented inline including per-value meanings. The description only echoes that query and filters can be combined, adding nothing the schema does not already contain, so the baseline 3 applies.

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 (search) plus the resource (Sophia Commons directory) and enumerates the entity types covered, so an agent can immediately tell this is a filtered directory lookup. It does not explicitly contrast itself with get_listing or find_nearby, so sibling differentiation is only inferable from the filtering language.

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 second sentence explains how to combine a free-text query with category/country/city filters, which implies usage. However, it never says when to prefer this over find_nearby (proximity) or get_listing (single record), nor any exclusions, so routing guidance is left to inference.

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