token_get_metadata

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

With no annotations present, the description must fully convey behavioral traits. It implies a read-only operation ('Fetch'), but lacks disclosure on side effects, authentication requirements, rate limits, or error behavior. This is insufficient for a tool with no annotation support.

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 extremely concise—one sentence. While brevity is positive, it omits critical details that could be included without much length, such as what metadata is returned. The mention of 'via Dritan' adds little value without context.

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 simple tool with one required parameter and no output schema, the description is incomplete. It fails to describe the response format, whether authentication is needed (other tools require API keys), or any other context that would help an agent use it correctly among many token-related siblings.

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 schema has 0% description coverage for the 'mint' parameter. The description does not clarify what 'mint' represents (e.g., token mint address) or provide any format or example, leaving the agent with no semantic guidance beyond the parameter name.

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 'Fetch token metadata via Dritan' clearly states the action (fetch) and resource (token metadata), with a specific data source mentioned. However, it does not differentiate from sibling tools like token_get_price or token_get_aggregated, which also fetch token-related data.

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 provided on when to use this tool versus the many sibling token tools (e.g., token_get_price, token_get_risk, token_get_aggregated). There is no mention of prerequisites or context for selection.

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