orbuc-mcp-server

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

Adds 'aggregated' context beyond readOnlyHint annotations, implying computed/summarized data. Does not disclose data freshness, historical range, or rate limits, but safety profile is covered by 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?

Front-loaded purpose statement with standard Args docstring. Efficient structure with minimal redundancy, though Args section repeats implied optionality.

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 simple single-parameter tool with good safety annotations. Missing pointer to segment discovery sibling (orbuc_btc_holdings_segments) and lacks aggregation methodology details given no output schema.

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, description provides basic semantics ('Segment name') and optionality. However, lacks enumeration guidance or reference to segment discovery sibling tool.

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' with specific resource 'weekly aggregated BTC holdings'. Temporally distinguishes from siblings (daily, current) via 'weekly', though does not explicitly contrast with segment-listing sibling.

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?

Mentions the filter is optional ('optionally filtered by segment') but provides no guidance on when to prefer this over daily/current variants or how to discover valid segment values.

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