gorelo_list_custom_assets

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

With no annotations provided, the description carries the behavioral burden. It discloses pagination behavior and ordering, and 'List' implies a read-only operation, but it does not explicitly state safety/no side effects, authentication requirements, or potential limitations. It adds useful context but not a complete behavioral profile.

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 states the action, resource scope, pagination, and ordering with no filler. Every phrase earns 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?

Given eight optional parameters, no annotations, and no output schema, the one-line description covers core purpose, pagination, and ordering but omits filter combination semantics and response shape. Agents may still need to infer how query, clientIds, and time filters interact.

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 75%, so the schema documents most parameters. The description adds pagination/ordering context relevant to cursor and pageSize, but it does not clarify the two undocumented parameters, query and clientIds. Their names and types provide partial meaning, but the description offers no extra semantic detail.

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 uses a specific verb ('List'), names the resource ('custom (non-agent) assets for the service provider'), and includes distinguishing traits (cursor-paginated, newest-created first). This clearly differentiates it from sibling tools like gorelo_list_assets and gorelo_list_clients.

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 qualifier 'custom (non-agent)' implies this tool is for non-agent assets and not the general gorelo_list_assets, but it never explicitly says when to use this tool versus siblings or when not to use it. No alternatives or exclusion conditions are named.

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