get_asset_metadata

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read operation and that it returns all metadata views/values, but it does not disclose response shape, pagination, possible size implications, or any relationship to the narrower get_asset_metadata_view. It is not misleading, but it is thin.

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 sentence with no filler, front-loading the verb and the object being returned. Every word contributes to the core purpose.

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 one-asset read operation with a single required parameter, and the description conveys the essential purpose. However, with no output schema or annotations, the phrase 'metadata views and values' is left undefined, and there is no indication of what an agent should expect in the result, so some context is missing.

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 coverage is 100%, so the sole parameter is already documented with its type, format, and description. The tool description adds nothing beyond the phrase 'for an asset,' which aligns with the existing asset_id description; this meets the baseline for high schema coverage.

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 desc. states a clear verb ('Get') and resource ('all metadata views and values for an asset'), so it is specific enough to identify the operation. It does not explicitly contrast with siblings like get_asset_metadata_view, but the 'all views' wording hints at a broader scope than a single view.

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 given on when to use this tool instead of related metadata tools such as get_asset_metadata_view, list_metadata_views, or get_collection_metadata. The context is implied but not stated, and there are no exclusions or alternatives.

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