Search Assets

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

With no annotations, the description carries the burden and mostly does: it discloses case-insensitive substring matching, exact group matching, combinability, and that passing neither filter returns ALL assets. That unbounded-default disclosure is genuinely useful. It stops short of pagination, result limits, or whether ordering is guaranteed.

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?

Front-loaded purpose followed by tight bullets, with the highest-value routing guidance last. The 'Returns per asset: ...' line partially duplicates the output schema and is the one sentence that does not fully earn 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?

An output schema exists so return values need not be spelled out, and the description nonetheless covers discovery intent, filter semantics, and the default-all behavior. Missing only pagination/limit behavior and any explanation of the 'env' parameter.

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 0%, so the description must compensate — and it documents prefix and group well, including matching semantics and examples. However, the third parameter 'env' is never mentioned in either the schema or the description, leaving a genuine gap.

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 and resource ('Search and list assets') and scopes it to two filter modes, name prefix and group. It also names the siblings it precedes (get_asset_details, get_asset_health), so the agent can separate discovery from detail/health lookups without opening a 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?

Explicit 'When to use' section names the downstream tools it feeds and prescribes which filter to pick ('prefix for fuzzy search, group for scoped listing'). It also states the no-filter fallback, removing the main ambiguity for an all-optional-parameter tool.

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