gorelo_get_asset

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Get' clearly implies a read-only operation, and there are no apparent side effects, but the description does not mention error behavior, authorization requirements, or whether the id refers to an asset id, agent id, or some other identifier.

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, concise sentence with no fluff. It front-loads the verb, resource, and key scoping detail ('by id'), which is exactly what an agent needs at a glance.

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?

For a simple single-resource lookup with one required parameter, the description is minimally adequate. However, it lacks any explanation of the return value or the meaning of 'id' in context, and there is no output schema to compensate for that missing information.

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?

With 0% schema description coverage, the description must compensate for the schema's silence on 'id'. Saying 'by id' mostly restates the parameter name and adds little meaning. It does not clarify what kind of id this is, what format it takes, or how it relates to the 'agent (managed device)' wording.

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 the operation ('Get'), the resource ('a single agent (managed device) asset'), and the lookup mechanism ('by id'). It is immediately distinguishable from sibling tools like gorelo_list_assets, which list assets rather than fetch a single 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?

The usage context is implied: use this tool when you need one specific asset by its id rather than a list of assets. However, there is no explicit comparison to gorelo_list_assets or gorelo_list_custom_assets, nor any guidance on when not to use this tool.

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