token_get_deployer_stats

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Fetch' implying a read operation, but does not confirm idempotency, data source (Dritan's role), or any side effects. This is insufficient for an agent to assess safety or expect return behavior.

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 very short (8 words) but lacks critical details. Conciseness is positive, but the trade-off is severe under-specification. It does not earn its place as it omits parameter usage, context, and behavioral information.

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 tool's single parameter and lack of output schema, the description is extremely incomplete. It does not explain what 'deployer stats' encompass, how to interpret results, or any constraints. This is insufficient for an agent to use 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?

The input schema has one required parameter 'mint' of type string, but the description does not explain its purpose (e.g., token mint address). With 0% schema description coverage, the agent has no additional meaning beyond the raw schema, which is inadequate.

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 verb 'Fetch' and the resource 'token deployer stats', indicating the tool retrieves statistics related to token deployers. While it doesn't explicitly differentiate from siblings, the resource name is distinct among the available tools, making the purpose reasonably clear.

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?

The description provides no guidance on when to use this tool versus alternatives, such as other token-related tools like 'token_get_metadata' or 'token_get_risk'. The mention 'via Dritan' hints at a dependency but does not clarify context or prerequisites.

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