orbuc-mcp-server

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

Annotations declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds valuable behavioral context not in annotations: the return content ('supply data') and structure ('chain breakdown'). No contradictions with annotations.

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?

Appropriately structured with purpose front-loaded in the first sentence, followed by parameter documentation. The 'Args:' block is slightly formal but efficient given the schema's lack of descriptions. No wasted words.

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?

Adequate for a single-parameter read tool: describes what it fetches (supply data with chain breakdown) and the required input. Would benefit from brief return value description since no output schema exists, but acceptable given the simple data retrieval pattern.

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?

Effectively compensates for 0% schema description coverage by providing the parameter's semantic meaning ('Stablecoin ticker'), concrete examples ('USDT, USDC'), and requirement status ('required')—critical context absent from the schema's bare 'title: Symbol'.

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?

Clear verb ('Get') and resource ('latest supply data'), with specific scope ('for a specific stablecoin with chain breakdown'). The 'specific' qualifier distinguishes from sibling aggregate tools like orbuc_stablecoin_latest, though it doesn't explicitly name the alternative.

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?

Implies usage context by specifying 'specific stablecoin,' suggesting use when per-coin data is needed rather than aggregate data. However, lacks explicit when-to-use guidance versus similar siblings like orbuc_stablecoin_coin (without _latest) or orbuc_stablecoin_chains.

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