delete_activity

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

Description implies destructive action but does not disclose reversibility, side effects, or permission requirements. Since annotations are absent, the description carries full burden but offers minimal behavioral context.

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?

Extremely concise with two sentences. No extraneous information. Structured 'Args' format aids readability.

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?

Tool is simple (one parameter, output schema exists). Description adequately states purpose and parameter but lacks usage guidance and behavioral details, leaving gaps for an AI agent's decision-making.

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 description provides a one-line explanation for the single parameter (activity_id). This adds value beyond the empty schema but is minimal and lacks format or constraints.

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?

Description clearly states the verb (Archive/delete) and resource (an activity in EARLY). It distinguishes from sibling tools like delete_time_entry by resource type, though it doesn't explicitly differentiate from other activity operations.

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 guidance on when to use this tool versus alternatives (e.g., update_activity or create_activity). No when-not-to-use advice or prerequisites provided.

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