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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It correctly indicates this is a destructive operation ('Remove...activity') and notes the authentication requirement ('Requires a bearer token'), which is critical for agent invocation. It could additionally mention irreversibility or side effects on the itinerary, but the current disclosure is still good.

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 only two sentences, front-loading the action and resource, then immediately providing the critical requirement. Every sentence earns its place with no wasted words.

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 low complexity (1 parameter, no output schema, no nested objects), the description covers the essential aspects: action, resource, and auth requirement. It does not explain return values, but there is no output schema to detail them, and for a deletion operation the return is typically minimal. A brief note on what happens upon success (e.g., 'no return content') would make it complete, but the current state is still nearly adequate.

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 single parameter activity_id is fully defined in the schema with type, format, and pattern, providing high structural clarity. However, schema description coverage is 0%, meaning the schema property has no description field. The tool description does not elaborate on activity_id any further, so it adds no meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 the specific verb 'Remove' with the resource 'activity from a concierge itinerary day', making the action and scope clear. It distinguishes this tool from siblings like delete_itinerary, which operates on a different resource.

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 states a prerequisite ('Requires a bearer token'), but provides no guidance on when to use this tool versus alternatives (e.g., update_itinerary or write_itinerary_day_detail). Sibling tools suggest possible alternatives for modifying itineraries, but the description does not address them.

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