end_activity

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

With no annotations provided, the description must fully convey behavioral traits. It does not disclose side effects (e.g., whether ending is irreversible), permissions required, rate limits, or what happens to the activity afterwards. The description only states the action and lists parameters.

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 structured as a docstring with parameter list, which is clear but somewhat repetitive (e.g., 'to show when the activity ends' appears multiple times). It could be more concise by grouping or removing 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 presence of an output schema and 7 parameters, the description covers parameter semantics but lacks details on return value, error handling, or lifecycle context. It is minimally complete for a simple mutative action.

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 description adds meaning to each parameter beyond the schema's property names, including brief explanations like 'The ID of the activity to end' and default values. With 0% schema description coverage, this is essential and well-handled, though some descriptions are slightly tautological.

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 tool's action: 'End an activity with a title and message.' This is a specific verb+resource combination that distinguishes it from sibling tools like start_activity and update_activity.

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 provides no guidance on when to use this tool versus alternatives such as update_activity or send_notifications. It lacks context on prerequisites, timing, or exclusions.

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