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

Annotations already indicate read-only (readOnlyHint=true) and non-open-world (openWorldHint=false). The description adds context about the data being 'Measured + AI data, not advice' and describes the macro regime construction, adding value beyond annotations without contradicting them.

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 longer than typical but well-structured, starting with a 'START HERE' cue and listing contents, alternatives, and a caveat. While not minimal, most sentences add useful context for a comprehensive snapshot tool.

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?

With no output schema, the description adequately enumerates the returned data: current price, market-state consensus, support/resistance, liq-map targets, and macro regime. It also notes the Pro tier restriction and data nature, making it complete for an agent to decide invocation.

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 schema has one param 'coin' with a default and 0% description coverage. The description references 'one coin' and the parameter name is self-explanatory, making the purpose clear. It does not specify valid value formats, but that is a minor gap for a single obvious parameter.

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 this is a 'Unified whole-system snapshot for one coin' and enumerates the specific data categories it returns. It also distinguishes itself from sibling tools by noting 'One call instead of stitching get_macro + get_market_state + get_levels' and listing drill-down alternatives.

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 explicitly tells when to use this tool: 'One call instead of stitching... Drill down only if needed: get_positioning...' This provides clear guidance on using it as the primary snapshot and points to alternatives for deeper detail.

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