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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'List recent Bitcoin notarization records' without explaining ordering, pagination, recency criteria, idempotency, or potential side effects. This is insufficient for an agent to safely invoke the tool.

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 wasted words. However, it omits critical usage context, which reduces its overall efficiency. The conciseness is good but comes at the cost of completeness.

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?

Despite having an output schema and two well-documented parameters, the description lacks essential context such as how 'recent' is defined, whether results are paginated, and what status filter options are valid. Given the absence of annotations, the tool description is too sparse for an agent to use reliably.

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%, meaning both parameters (limit, status) are already described in the input schema. The description adds no additional meaning or context beyond the schema, so baseline 3 is appropriate.

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?

Description explicitly states 'List recent Bitcoin notarization records', providing a specific verb ('List') and resource ('recent Bitcoin notarization records'). This clearly distinguishes it from sibling tools like 'weather_get_notarization_proof' (retrieves a specific proof) and 'weather_notarize_ledger' (creates a notarization).

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?

No guidance on when to use this tool versus alternatives. Siblings such as 'weather_get_notarization_proof' exist for more targeted operations, but the description does not indicate when listing is appropriate or when to prefer a different tool.

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