List Sandcastle markets

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds that the markets are 'curated' and 'leveraged-liquidity', giving a bit of context on composition, but no mention of response format or pagination. With high annotation coverage, the bar is lower, and the description adds modest value.

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?

Single sentence, front-loaded with the core action 'List markets', and includes the key differentiator 'deployment addresses'. 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 zero-parameter read-only list tool with annotations covering safety, the description is complete. It tells the agent what it returns (markets and addresses). The only minor gap is not mentioning the response format (e.g., array), but that's often implicit for list tools and no output schema is provided.

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 zero parameters, schema coverage is trivially 100%. The description doesn't need to explain parameters; the baseline for 0 params is 4, and the description appropriately focuses on what the tool returns.

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 the tool lists curated markets and their deployment addresses, with a specific verb 'List' and resource 'markets'. It distinguishes itself from sibling tools like get_market (which likely retrieves a single market) and get_positions (which deals with positions).

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 this is the entry point for discovering available markets, but doesn't explicitly state when to use it over others. Since it has no parameters and siblings are named, an agent can infer it's for overview. A brief 'use this to get all markets' would bump to 5.

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