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

With no annotations provided, the description carries full burden. It mentions included fields (firstSeenAt, ledgerVerified) but no other behavioral traits like ordering, pagination, error conditions, or side effects. For a tool that likely returns a list, this is insufficient.

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 brief but the first sentence is somewhat awkward and could be clearer. It front-loads the differentiator but wastes no words. However, conciseness is not achieved at the expense of completeness, which suffers.

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 simplicity (1 param, no output schema, no annotations), the description does not adequately equip the agent. Missing details on response structure, limits, or prerequisites make it incomplete for effective use.

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 only parameter itemId has no description in the schema (0% coverage). The description does not explain what itemId represents or its format, leaving the agent without guidance on how to populate the required field.

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 for a real-estate record and distinguishes it by focusing on when the record appeared or was revised. This differentiates it from sibling tools like get, recent_changes, search, and verify_ledger.

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 usage for historical timeline queries but does not explicitly state when to use this tool versus alternatives like realestate_watch_recent_changes or realestate_watch_get. No when-not-to-use or prerequisite guidance is provided.

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