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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent knows it's a destructive operation. The description adds the scope (an activity from a trip) but does not disclose side effects like cascading deletions or irreversibility beyond the annotation's implication. Given the strong annotation coverage, this is adequate.

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 a single sentence, highly concise, and front-loaded with the action. Every word is necessary and provides clear meaning. There is no verbosity or redundancy.

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 simplicity of the tool (one parameter, no output schema, no nested objects), the description is sufficiently complete. It states the action and the resource. It could mention that the deletion is permanent or that the activity must exist, but the annotation (destructiveHint) covers the destructive nature. Overall, it meets the needs for a simple delete operation.

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%, but the tool has only one parameter (activity_id). The description implicitly conveys that the parameter is the identifier of the activity to delete, but it does not explicitly state the format or source. Since the schema provides the name and type, and the tool's purpose is clear, the description adds enough context for a single simple parameter.

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 'Remove an activity from the trip.' clearly specifies the action (remove) and the resource (activity from a trip). It is distinct from sibling tools like delete_accommodation or update_activity, so the agent can easily identify what this tool does.

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 the tool: when you need to remove an activity from a trip. It does not explicitly state when not to use it or mention alternatives (e.g., for deleting other resources). However, the context is clear enough for a simple delete operation.

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