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

With no annotations, the description carries the full burden. It accurately describes what the tool returns (fee and anchor-fee share), but does not disclose whether the quote is guaranteed, whether any side effects exist, or if there are rate limits. The 'preflight' wording hints it is a non-mutating quote, but this is not explicitly stated.

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, front-loaded sentence that conveys all essential information without unnecessary words. It is perfectly sized for a tool with no parameters.

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?

Given the low complexity (0 params) and the presence of an output schema, the description is sufficiently complete. It states the core purpose and contents of the quote. However, it does not mention how this fits into the broader timestamping workflow (e.g., that it should be called before timestamp_hash), so it is not fully contextually rich.

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 an empty properties object, so there is no schema to clarify. The baseline for 0 params is 4, and the description correctly focuses on the tool's output rather than dwelling on non-existent parameters.

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 resource as 'current Bitcoin timestamping preflight quote'. It also specifies the contents (fixed service fee and estimated anchor-fee share), which distinguishes it from sibling tools like timestamp_hash and verify_timestamp.

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 tool is used before performing a Bitcoin timestamping operation ('preflight quote'), but it does not explicitly state when to use it versus alternatives or mention any exclusions. No alternative tools are named, so guidance is only implied.

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