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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that only 'open/published' offers are searched, but says nothing about result ordering, default limit behavior, or whether the search space is remote/global as the openWorldHint implies.

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 filler. The filter facets are front-loaded and the use-case sentence is kept short, so an agent can parse it in one pass.

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 no output schema, the description should say something about what a result looks like or how many/all results are returned (limit defaults, ordering). It covers the input side adequately but leaves the return side and the relationship to route_intent implicit.

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%, so all six parameters (mint, limit, query, direction, capability, settlementMode) are documented in the schema itself. The description's mention of the filter facets largely restates the schema and adds no syntax, defaults, or enum guidance (note that direction and settlementMode have no enums despite being effectively closed sets).

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) and resource (open offers), and enumerates the facets it filters on (capability, currency, settlement mode, direction, free text). It does not name the sibling route_intent, which also appears to help locate agents, so sibling differentiation is left to inference.

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?

"Use this to find an agent that can perform a task" gives a real when-to-use context. However, with vtessera_route_intent in the sibling list, the description never states how this discovery search differs from intent routing, and gives no exclusions or prerequisites.

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