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

Annotations already provide readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about what can be changed but doesn't disclose additional behaviors like validation between start/end dates or partial-update semantics. Since annotations are strong, the description's marginal value is sufficient for a 3.

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?

A single, front-loaded sentence with zero redundancy. It names the three key actions (rename, correct dates, correct timezone) efficiently. Slightly more specific language about partial updates would push it higher, but it's already concise and well-structured.

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 tool has 5 parameters but only one required, and no output schema. The description explains the purpose but doesn't cover edge cases like what happens if only end_date is provided, validation between start/end dates, or the meaning of default_tz_offset (though the schema defines it). For a mutation tool with multiple optional fields, this is a moderate gap.

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 provides 100% coverage with descriptions for all five parameters. The description groups them (title, dates, timezone) which adds minor organization but no new semantic meaning beyond the schema. It doesn't hint at relationships between fields (e.g., date ordering). Baseline 3 is appropriate when the schema carries the bulk of the load.

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 clear verb ('rename/correct') and resource ('trip'), and specifies the exact attributes (title, dates, default timezone). It distinguishes from sibling tools like create_trip, update_block, and set_trip_ending, though it doesn't explicitly name a sibling as an alternative.

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 when to use this tool (to rename or correct a trip's dates/timezone) but doesn't explicitly contrast it with siblings like set_trip_ending or set_trip_head, which modify specific fields. An agent would infer usage from context but without explicit exclusions, it's adequate but not exceptional.

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