run_asset

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

Discloses read-only nature and fallback to sampleData, which is helpful since no annotations exist. However, lacks details on data freshness, error handling, or limitations of 'supported' assets.

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?

Single sentence with no redundancy. Front-loads key action ('return read-only live data') and includes fallback context efficiently.

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?

No output schema and minimal parameter descriptions. The description gives high-level purpose but not enough for an agent to understand return format, parameter constraints, or integration with sibling tools.

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 only 33% (only 'params' has a description). The description does not clarify 'asset_id' or 'limit' beyond the schema's basic definitions, leaving agents to infer usage.

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?

Clearly states it returns read-only live data for a Metabase/PostHog asset with a fallback mechanism. Distinguishes from siblings like 'get_asset' (metadata) and 'search_assets' (search) by specifying live data retrieval.

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 like 'get_asset' or 'trace_asset'. Does not specify prerequisites (e.g., asset must be supported) or context for the fallback behavior.

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