get_drawing_asset

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

No annotations are provided, so the description must disclose behavioral traits. It only states what is returned, but does not mention that the operation is read-only, safe, or any error behavior. Important safety context is missing.

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, front-loading the purpose and key return fields. No wasted words; efficient and easy to parse.

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 the output schema exists, the description does not need to detail return structure. However, it lacks context on error handling, required permissions, or how this tool relates to similar tools. Adequate for a simple get operation but incomplete for decision-making.

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 adds no meaning for the required parameter 'asset_id'. It does not explain its format, constraints, or how to obtain it. The description fails to compensate for the lack of schema documentation.

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 tool returns a single drawing asset, specifying three aspects: provenance, scale guidance, and availability. This distinguishes it from sibling tools like list_drawing_assets (which lists many) and other get_* tools focusing on different resources.

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?

Usage is implied for retrieving a specific drawing asset by ID, but no explicit guidance on when to use this vs alternatives like list_drawing_assets or get_diagram_asset is provided. No exclusions or contextual hints given.

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