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

With no annotations, the description carries the full burden. It mentions key fields (firstSeenAt, ledgerVerified) but does not disclose whether the tool is read-only, the number of events returned, pagination, or any behavioral traits beyond the basic purpose. The term 'time-ordered events' is vague.

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 one sentence, efficient and front-loaded with the core purpose. However, it could be more structured to separate purpose from field listing. Still, it wastes no words.

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 simple inputs (one required param, no output schema), the description is minimally adequate. It explains the tool's focus and key fields but lacks details on event structure, order, or limits, which would be helpful for an agent.

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 single parameter (itemId) has 0% schema description coverage. The description does not explain what itemId represents (e.g., sanction ID), assuming domain knowledge. The schema already defines it as a string without further context.

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 clearly states it returns 'time-ordered events only for a sanction' and highlights the differentiator ('when it appeared and when it was lifted'). It also mentions included fields (firstSeenAt, ledgerVerified), making the tool's unique value distinct from siblings like sanction_watch_get or sanction_watch_search.

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 for timeline events ('time-ordered events only'), but it does not explicitly state when to use this over alternatives like sanction_watch_get or sanction_watch_recent_changes. No when-not or alternative guidance is provided.

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