search_flexible_assets

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

No annotations are present, so the description must carry behavioral disclosure. It only restates the required filter, which the schema already marks as required, and does not address pagination behavior, permission requirements, error semantics, or response format.

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 a single front-loaded sentence with no wasted words. The parenthetical requirement is efficient and easy to parse.

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?

The description is adequate for a straightforward search tool: the purpose and mandatory filter are stated, and the schema covers parameter details. It is thin on surrounding workflow context such as how to obtain the type ID or what the response looks like, but it is not dangerously incomplete.

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 includes descriptions for all six parameters, so parameter semantics are mostly covered by the schema. The description adds little param-level meaning beyond restating the required filter.

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 that the tool searches flexible assets in IT Glue, naming the verb and resource clearly. It also flags the required filter, distinguishing it from sibling tools like list_flexible_asset_types, which lists types rather than assets.

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?

The required flexible_asset_type_id gives a clear precondition for using the tool. However, it does not explicitly state when to prefer this tool over related tools or what conditions would make it inappropriate.

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