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

Goes well beyond the annotations by disclosing lifecycle and visibility behavior: the program's current state is snapshotted, a new trip starts as DRAFT, and it is not listed on the company website until publish_trip is called. These are exactly the non-obvious side effects an agent needs for a create-mutation.

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?

Three sentences, front-loaded with the core action, then the field list, then the lifecycle note. It is dense but each clause earns its place; the parenthetical field list is slightly cramped but not wasteful.

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 creation tool with 0% schema coverage, the description covers all parameters, the required one, the snapshot/draft semantics, and the publish hand-off. An output schema exists, so return values need not be described; nothing essential is missing.

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 0%, so the description carries the full burden and does: programId is flagged REQUIRED uuid, dates are YYYY-MM-DD, maxParticipants uses null = unlimited, and timezone is an IANA name with an example. This adds format and semantic meaning the schema alone does not convey.

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+resource ('Create a new TRIP from a program') and immediately distinguishes it from publish_trip and from create_program/create_template by naming the source entity. An agent can identify the operation and its lineage without opening the schema.

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?

Provides clear context for use (a trip is always a live instance of a program, program state is snapshotted) and names the follow-up alternative publish_trip for the open-for-sale case. It stops short of stating exclusions such as when to create a program/template instead, so it is clear but not exhaustive.

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