Pricing Information

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

No annotations are provided, so the description bears full burden. It discloses a key behavior: the tool does not start a payment. However, it omits other important traits such as authentication requirements, rate limits, or whether it caches data. Adds some value but could be more comprehensive.

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 a single sentence with no unnecessary words. It is front-loaded and efficient, earning its place without redundancy.

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?

An output schema exists (not shown but noted), so the description does not need to detail return structure. It covers the high-level content—pricing, starter-credit positioning, settlement guidance. Could benefit from briefly explaining what 'settlement guidance' entails, but overall it is sufficient for a parameterless info tool.

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 tool has zero parameters, and schema description coverage is 100% (vacuously). The description does not need to add parameter meaning. With no parameters, a baseline score of 4 is appropriate; the description provides adequate context for 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 uses a specific verb 'Return' and clearly identifies the resources: Blocksize pricing, starter-credit positioning, and settlement guidance. It distinguishes itself from sibling tools like get_product_catalog or get_market_data_endpoint by noting 'without starting payment,' implying this is an information-only endpoint.

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 phrase 'without starting payment' suggests this tool is for previewing pricing and guidance before initiating a payment, but there is no explicit comparison to sibling tools or mention of when not to use this tool. Adequate but lacks clear exclusion criteria.

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