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

The description adds value beyond the readOnlyHint annotation by explaining that results are chronologically ordered and include timestamps, types, and verification status. This gives the agent a clear expectation of the output structure. While it doesn't mention pagination or limits, for a read-only timeline tool this is useful behavioral context.

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 extremely concise: two sentences, no filler, front-loaded with the core action and resource. It efficiently communicates scope, filtering, and return format. Every word 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?

For a read-only list tool with well-documented parameters, no output schema, and a simple return format, the description is complete. It covers what the tool does, the filtering capability, and the nature of the returned events. The complexity is low and the description adequately addresses it.

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 schema already describes all parameters with 100% coverage. The description's mention of 'Filter by date range' simply restates the start_date and end_date parameters without adding new meaning. It also mentions 'property or specific booking' which maps to property_id and booking_id, but again this is already clear from the schema. No extra semantics are provided.

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 uses a specific verb 'Get' with a clear resource: 'chronological timeline of all evidence records for a vacation rental property or specific booking.' It further clarifies the output (events in order, timestamps, types, verification status), making it distinct from sibling tools like query_vacation_rental_evidence_chain which likely focus on chain integrity rather than timeline presentation.

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 context: use this for a vacation rental property or specific booking, optionally filtered by date range. However, it does not explicitly mention alternatives or when not to use this tool, such as comparing with query_vacation_rental_evidence_chain or verify_vacation_rental_evidence_record. The guidance is implied rather than explicit.

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