ldbd_get_asset

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

With no annotations, the description carries the full burden. It discloses the return content (closes and sentiment), but does not mention read-only behavior, permissions, or output format. 'Full info' is slightly broad, yet the specifics help.

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 that wastes no words. It immediately states the action and the key 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?

For a simple one-parameter tool with no output schema, the description gives a reasonable high-level overview. However, it lacks detail on output structure, specific timeframes, or how sentiment is represented, which could be important for an agent.

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?

The only parameter, 'symbol', is not explicitly explained, but the phrase 'on an asset' implies that the symbol identifies the asset. This provides more meaning than the bare schema, though a more explicit definition would improve clarity.

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 it retrieves asset information, specifically 30-day closes and community sentiment per timeframe. A specific verb and resource are present, and the return content distinguishes it from sibling tools like searching or chart indicators.

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 by the description—this tool provides detailed asset information—but there is no explicit guidance on when to use it over alternatives, nor are any exclusions or predecessor conditions mentioned.

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