orbuc-mcp-server

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about what data is retrieved (supply distribution across specific chains) but omits details about rate limits, authentication requirements, or what the tool returns when 'days' is null versus populated.

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 appropriately compact with two distinct sections: a clear purpose statement followed by an Args block. Every sentence provides necessary information without redundancy, making it easy to parse.

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 single-parameter schema and comprehensive annotations, the description covers the essentials but lacks information about the return format (no output schema exists) and doesn't clarify the default behavior when 'days' is omitted (current snapshot vs. all historical data).

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?

With 0% schema description coverage, the description fully compensates by documenting the single 'days' parameter in the Args section, explaining it controls 'Number of days of history' and noting it is optional. This provides sufficient semantic meaning missing from the structured schema.

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 tool 'Get[s] stablecoin supply distribution across chains' and provides concrete examples (Ethereum, Tron, Solana), effectively distinguishing it from sibling tools like 'orbuc_stablecoin_coin' or 'orbuc_stablecoin_aggregate'. However, it doesn't explicitly contrast usage scenarios with these siblings.

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 like 'orbuc_stablecoin_aggregate' or 'orbuc_stablecoin_latest', nor does it explain when to provide the 'days' parameter versus omitting it for current data.

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