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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds important operational context: the data comes from a snapshot refreshed about every 15 minutes, includes 'when it was last observed', and should not be used when latest intraday detail is required.

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 front-loaded with the core purpose and return contents, followed by source freshness and sibling routing. Although dense, every sentence contributes decision-relevant information without restating annotations or schema details.

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?

There is no output schema, but the description lists the key returned fields and explains the snapshot freshness model. Combined with a fully documented input schema and safety annotations, it gives enough information to invoke and interpret the tool correctly.

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 description coverage is 100%, and the schema already explains the symbol format and the optional type enum behavior. The description only says the lookup is 'by symbol', so it adds little parameter-level detail beyond the schema baseline.

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?

States a specific verb and resource: 'Look up one asset by symbol' and enumerates the profile fields returned. It clearly distinguishes a profile/snapshot lookup from a quote, intraday, or bulk lookup.

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?

Explicitly identifies this as the default for 'what is X' or 'how is X doing' and names the alternatives: get_asset_quote for latest/intraday detail and get_assets_bulk for several symbols. This gives clear routing guidance.

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