get_sovereign_reserves

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explains filter semantics (case-insensitive substring, tier ranking) but does not mention output format, sorting order, data freshness, or any side effects. The read-only nature is unstated, and the return shape is left undefined.

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 and well-structured with an 'Args' block. The opening phrase 'Sovereign Bitcoin holdings, ranked' is efficient but could be improved with a verb to form a complete sentence. Every line earns its place with 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?

For a simple lookup tool with two optional parameters, this is adequate but has gaps. The description covers purpose and parameters but fails to specify what the response contains, which is critical given there is no output schema. It also lacks any caveats about ranking criteria or data scope.

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?

Schema description coverage is 0%, so the description must compensate. It does so by explaining 'country' as a case-insensitive substring and 'tier' as a rank filter with '1 = largest holders'. This adds meaningful context beyond the bare schema types and clearly conveys how filters behave.

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 identifies the resource (sovereign Bitcoin holdings) and indicates a ranked list, which is clear. However, it lacks an explicit verb like 'get' or 'list', making it a fragment rather than a full purpose statement. It does not explicitly distinguish from the sibling 'get_treasury_holdings', though the 'sovereign' qualifier provides some differentiation.

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 gives no guidance on when to use this tool versus alternatives like get_treasury_holdings or get_hiring_signal. It implies usage for sovereign holdings but does not state exclusions, prerequisites, or scenarios where another tool would be more appropriate.

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