Get live Sandcastle market state

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is handled. The description adds useful context that the tool reads three distinct pieces of data (market, pool, and stored Morpho totals) from a specific chain, which is not visible in the annotations alone.

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?

Two sentences deliver all essential information: the first states the operation and resources, the second specifies the accepted input forms. There is no filler or redundancy, and the content is front-loaded with the core action.

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 single-parameter, read-only tool with strong annotations, the description is reasonably complete. It tells the agent what data will be accessed and what the parameter can be, though it does not mention the output structure, which is a minor gap given the absence of an 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?

The input schema already describes the single 'market' parameter as 'Market id, pool address, or Morpho market id', with 100% schema description coverage. The description repeats this without adding further meaning, so it earns the baseline score.

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 uses the imperative verb 'Read' and names specific resources: a Sandcastle market, its Uniswap V3 pool, and stored Morpho totals from Robinhood Chain. It clearly differentiates from sibling tools like list_markets by focusing on a single market and by listing multiple identifier forms it accepts.

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 implies the tool is used when you need state for a single market, but it does not explicitly contrast it with list_markets or get_positions, nor does it explain when to avoid this tool in favor of a sibling. The context is present but not directly stated.

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