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

With no annotations, the description carries the burden and does well: it discloses matching semantics, exact person-match behavior, Japanese/English support, date formats (YYYY-MM-DD or YYYY-MM), return fields including countries, date type, and source URL. It does not mention pagination or default limit behavior, but the core behavioral profile is substantially covered.

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 front-loaded with the core purpose and database scope, then quickly covers matching behavior and return values. It is dense but every sentence contributes useful information; there is little filler.

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?

For a complex search tool with no output schema and no annotations, the description supplies the essential context: what is searchable, matching rules, language support, date range, and return fields. It still leaves gaps around sibling choice, genre filtering, and limit/year filter semantics, but the overall coverage is solid.

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 only 20%, so the description must compensate. It meaningfully expands the required q parameter (titles, English titles, people such as artists/directors/authors, Japanese/English) and gives the overall category scope, but it does not explain the 31-value genre enum, the year_from/year_to filters, or the limit parameter beyond the schema's bare types.

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: 'Search ChronoDrawer', and scopes it as a month-by-month database from 1960-2026 covering events, media, people, and more. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as get_entity, get_month, on_this_day, or person_timeline.

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?

Usage is implied through the matching behavior: titles, English titles, people, and Japanese/English queries. However, the description gives no explicit guidance on when to use this tool versus siblings like person_timeline for a person or on_this_day for a date, and no exclusions are stated.

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