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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is known. The description adds real behavioral context: append-at-end placement, real-time sync to tripmates on shared trips, that it runs without confirmation because remove_place undoes it, and the required Cotlet API key scope.

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?

Front-loaded with purpose and destination, then supporting behavior. Every sentence carries some information, though the shared-trip sync line is slightly peripheral for a call-preparation reader.

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 6-param mutation with no output schema and full annotation coverage, the description supplies placement semantics, sync behavior, undo, and auth requirements. It omits any hint of the return value (e.g., the created place entry), a minor gap given no output schema exists.

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 100%, so the schema already documents all six parameters, including defaults. The description adds only the placement semantics ('end of the day') which maps loosely to behavior rather than to specific parameters. Baseline 3 applies.

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?

States a specific verb (add) and resource (place) plus both possible destinations (a day of the itinerary or a list). This cleanly distinguishes it from sibling tools like wanderlog_add_note or wanderlog_add_hotel.

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?

Clearly explains the day-vs-list selection rule ('or of the list when no day is given') and names remove_place as the undo path. It does not, however, route against search_places or add_hotel for related cases, so it stops short of full alternative coverage.

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