swarmtrade_search_assets

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

No annotations are provided, so the description carries the burden. It states the tool searches 'registered assets' (implying a subset) and filters by type/status/limit, but does not disclose pagination, ordering, or whether results are real-time. Minimal behavioral context beyond basic functionality.

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 concise (two sentences) and front-loaded with the core purpose. Every word adds value, and there is no redundancy or filler.

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 4 optional parameters, no output schema, and no annotations, the description adequately covers the tool's role as a filtered search. It does not explain return structure or pagination, but for a simple search tool this is acceptable. Siblings are distinct, reducing confusion.

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%, so the baseline is 3. The description reiterates the filter parameters ('type, status, or limit') but adds no additional meaning beyond the schema's own descriptions. No examples, defaults, or constraints are given.

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 explicitly states the verb 'Search' and the resource 'registered assets', differentiating it from sibling tools which focus on actions like announcing, trading, or resolving disputes. The mention of filters (type, status, limit) clarifies the scope.

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 description implies usage for searching assets but does not specify when to use this tool versus alternatives (e.g., when to use search vs other tools). No exclusion or when-not-to-use guidance is provided. Siblings are mostly transaction-oriented, so the purpose is clear but not explicitly contrasted.

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