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

No annotations are provided, so the description must carry the behavioral burden. It discloses that it's free, includes trial status, and that detail=full adds quota/pass/onboarding, which is useful. However, it never explicitly states the operation is read-only, side-effect-free, or idempotent, nor does it warn about rate limits or token consumption. For a simple manifest retrieval this is acceptable but not fully transparent.

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?

A single, dense sentence that front-loads the critical 'Start here (free)' signal, then lists contents, guidance to siblings, and parameter semantics. Every clause adds value; no fluff. The structure is logical and scannable.

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?

The tool has only 2 parameters, both fully described in the schema, and no output schema. The description explains what the manifest contains (tools, prices, trial status, journeys) and how to adjust detail level. It does not specify the exact return format, but for an overview tool that's a minor omission. Given the simplicity, the description is reasonably complete.

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 100%: both 'detail' and 'locale' are described. The description adds a small extra semantic by noting 'Compact includes arguments' (the schema only says 'Default compact' without specifying contents). It also reiterates the 'full' behavior, which is redundant. Overall it adds marginal value beyond the schema, but not enough to raise above baseline 3.

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?

States a specific verb+resource: 'Start here' and 'get_agent_manifest' clearly indicates fetching the manifest of the 4 tools, including prices, trial status, and journeys. It explicitly names the three sibling tools, distinguishing itself as the overview rather than the individual tools. No ambiguity.

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 says 'Start here (free)' which tells the agent this is the entry point, and 'Choose liquidation radar, native BTC/ETH depth or Li.Fi swap' indicates that after retrieving the manifest, the agent should select one of those tools. It does not explicitly say 'use this when you need to decide which tool to use' or exclude cases, but the intent is clear. It lacks explicit alternatives or when-not-to-use guidance beyond the implicit start-here positioning.

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