search_diagram_assets

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

With no annotations provided, the description carries the full burden of revealing behavior. It only says 'searches', failing to disclose pagination, filtering behavior, or any constraints (e.g., case sensitivity, fuzzy matching). This is a significant gap.

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?

The description is extremely short (one sentence) but under-specified. It sacrifices informativeness for brevity, failing to earn its place by providing necessary context. It would benefit from more detail.

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?

Given the complex input schema (7 parameters) and 31 sibling tools, the description is far from complete. It does not clarify how search differs from list, what the output schema returns, or any usage nuances. The presence of an output schema does not excuse the lack of context.

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?

The input schema has 7 parameters with 0% description coverage in the schema itself. The description does not explain any parameters (e.g., what 'category', 'query', or 'max_width_mm' mean), leaving agents to infer from names alone. It adds no value beyond the schema.

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 'Searches the diagram asset library' clearly states the tool's purpose: to search for assets. It implicitly distinguishes from siblings like 'list_diagram_assets' (which lists all) and 'get_diagram_asset' (which retrieves a specific one).

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 guidance is provided on when to use this tool versus alternatives like 'list_diagram_assets' or 'search_drawing_assets'. The description does not mention any prerequisites or context for its use.

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