search_catalog

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower, yet the description adds almost nothing beyond the filter list. It does not state whether multiple filters combine with AND semantics, whether results are ordered or limited, or what an empty match returns.

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?

A single front-loaded sentence with the action first and the filter dimensions after; nothing is redundant or padded. It is efficient, though one additional clause on combination semantics would have earned 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?

For a zero-required-parameter read-only filter tool with fully documented schema and annotations, this is adequate to invoke correctly. Gaps remain on result behavior (ordering, limits, empty results) which the description cannot defer to an output schema that does not exist.

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%, including enum values for category and form_factor, so the schema carries parameter meaning. The description merely re-lists those same fields in prose and adds no filtering semantics (combination logic, units, matching behavior) beyond what the schema already documents.

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?

The description gives a specific verb and resource ("Filter hardware blueprints") and enumerates the filter dimensions, which distinguishes it from get_device_blueprint (single lookup) and define_custom_blueprint (creation). It stops short of explicitly naming a sibling, but the search/filter intent is unmistakable.

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?

No when-to-use guidance is given: nothing says whether this must be called before mount_equipment, whether an empty result set is expected, or how this differs from get_device_blueprint. The list of filters implies a search use case but leaves selection to inference.

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