Resolve Asset By Source

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the agent knows this is a safe, idempotent read operation. The description adds the resolution behavior but does not disclose return format, error conditions, or whether it accesses local storage, adding minimal context beyond what annotations provide.

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 redundant or filler content. It is easy to parse and appropriately sized for a tool of this simplicity, though it is terse.

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 read-only tool with full schema coverage and safety annotations, this is minimally adequate, but it leaves key gaps: what 'resolve' returns (e.g., asset ID versus asset metadata), and when to use it over sibling asset lookup tools. Without output schema or more descriptive context, the agent may not know the expected result or invocation context.

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?

Both parameters have descriptions in the schema, giving 100% schema coverage. The description does not add further meaning beyond the schema, so it appropriately relies on the schema for parameter semantics.

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 and resource: 'resolve an asset' from a knowledge base document's source path, indicating a lookup operation. It is clear enough, though 'resolve' is somewhat domain-specific and it doesn't explicitly differentiate from sibling asset tools like get_asset or search_user_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?

No guidance on when to use this tool versus alternatives such as get_asset or search_user_assets. It does not mention prerequisite conditions, such as the need for a valid rag_id or a properly formatted source path, or what to do if the asset is not found.

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