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

With no annotations, the description must carry the full burden for behavioral disclosure. It states 'Requires a bearer token,' which is a useful authentication requirement. However, it does not describe whether updates are partial or full replacements, the side effects of changing is_public, or any rate limits. The token requirement adds value but there remains significant opacity.

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?

Two sentences with no filler. The first sentence conveys purpose and scope; the second adds an essential prerequisite (bearer token). It could be slightly more structured (e.g., listing fields), but for a simple update tool it is appropriately concise.

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 lack of output schema and the moderate parameter count (5), the description is adequate but not thorough. It omits common return values (e.g., 'Returns the updated itinerary object'), error cases, or idempotency behavior. It also does not clarify that only the provided fields are updated. For a mutation tool, this leaves gaps.

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 only 20% (only is_public has a description). The description lists the parameter categories (title, description, dates, public status) but does not clarify formats, constraints, or relationships. For example, 'dates' ambiguously maps to start_date without confirming whether end_date is omitted or separate. The explanation adds marginal value over parameter names.

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 the verb (Update) and the resource (concierge itinerary) and specifies the metadata fields (title, description, dates, public status). This sufficiently distinguishes it from sibling tools like create_itinerary (which creates) and delete_itinerary (which deletes).

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?

No explicit guidance on when to use this tool versus alternatives like create_itinerary or partial updates via other tools. The description does not mention prerequisites (existing itinerary) or when not to use it. An agent would have to infer from the tool name.

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