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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the timezone (Asia/Shanghai), that reviewedAt is a source-review date not a publication date, and the pagination size (20 items per page). The pagination and date field semantics are valuable additions for correctly interpreting results.

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 four efficient sentences, front-loaded with the core purpose and immediately covering the date format, default behavior, important semantic distinction, and pagination. Every sentence earns its place.

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 description covers the date semantics, timezone, default behavior, pagination, and clarifies the meaning of reviewedAt. Since an output schema exists, return value details are not needed. It omits guidance on the 'product' and 'language' parameters, which an agent might need to use correctly, but overall it is substantially complete for a read-only index 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?

Schema description coverage is 0%, so the description must compensate for parameter documentation. The description explains the 'date' parameter ('YYYY-MM-DD calendar day') and the default behavior ('Omit date for today'), but provides no guidance on the 'product', 'language', or 'page' parameters beyond what the schema's enum/default values already imply. With 4 parameters and no schema-level documentation, the description partially compensates but leaves significant gaps.

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 states a specific verb and resource: 'Read public items dated on a real YYYY-MM-DD calendar day in Asia/Shanghai.' It also disambiguates from botclaw_get_latest implicitly through 'date index, not an AI-generated daily report' and defines scope well. It doesn't explicitly name siblings like botclaw_get_latest or botclaw_search, so it falls short of a 5.

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?

It says 'Omit date for today,' giving a clear default and usage context. However, it doesn't explain when to use this versus botclaw_get_latest or botclaw_search, so sibling selection remains partially unclear.

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