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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully notes scope (single model vs all models) and that matching spans names and descriptions, but says nothing about result ordering, pagination, or truncation when hits exceed the limit.

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, zero waste, and the high-value routing hint (prefer this over repeated describe_entity calls) is placed immediately after the purpose statement.

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?

No output schema exists, yet the description never characterizes the result shape (hit counts, whether matches are ranked, what a hit contains). For a simple, well-annotated lookup tool the definition is otherwise sufficient to call correctly.

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 term, limit, model and all_models are all documented inline with defaults and maximums. The description only restates the search field concept, adding no syntax or format guidance beyond the schema; 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 ('Find') and the exact resource set (entities, fields, relationships, metrics) with its scope (a model or all models). It also names the sibling it replaces (describe_entity), so an agent can route between them without opening either schema.

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 a concrete when-to-use condition ('Faster than calling describe_entity repeatedly') with example phrasings like 'the overdue one' or 'whatever holds revenue'. There is no explicit when-not or exclusion case, but the alternative and its selection condition are clear.

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