filter_assets

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

There are no annotations, so the description must carry the burden of disclosing behavioral traits. It does not mention whether the operation is read-only, how filtering semantics work (e.g., AND/OR logic), or any permissions or rate limits. The description only restates the core filtering action and parameter meanings, adding no behavioral context beyond what is obvious.

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 concise and well-structured: one purpose sentence followed by a formatted Args list. Every sentence is useful and there is no fluff or repetition of schema metadata.

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 tool is a simple filtered list operation with an output schema, so the description need not explain return values. However, it lacks usage context (when to choose this over siblings), query language details, and any behavioral notes. It is minimally viable but not fully complete for an agent to invoke correctly without further guidance.

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. It provides brief meanings for each parameter and two query examples for the 'query' field, which adds value over the bare schema. However, it does not explain query syntax nuances (e.g., operators, combining conditions) or pagination behavior in detail, leaving gaps for a new user.

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 clearly states 'Filter assets using Freshservice query language' with a specific verb ('filter') and resource ('assets'). It distinguishes from sibling tools like get_assets (which likely lists all assets) and search_assets (which may use a different search mechanism).

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 such as get_assets or search_assets. While query examples are given, there is no explicit statement of appropriate use cases, exclusions, or how this tool differs from siblings.

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