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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds value by specifying that deletion is permanent and requires explicit user confirmation, which goes beyond the mere destructive hint and clarifies the irreversible nature of the operation.

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?

Two short sentences, no filler. The primary action is front-loaded, and the confirmation requirement is stated immediately. Every word earns its place.

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 delete tool with annotations and fully described parameters, the description covers the essential behavior: what is deleted, that it is permanent, and that confirmation is required. It does not explain return values, but no output schema exists and it is not critical for a delete operation. It is adequate but could mention potential side effects, though 'permanently' largely covers that.

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 input schema has 100% description coverage for all three parameters, so the baseline is 3. The description does not add extra meaning beyond the schema; it simply reiterates the confirmation requirement, which is already documented in the confirm parameter description.

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 states a specific verb ('delete'), a specific resource ('time activity'), and the context ('from QuickBooks Online'). It also adds 'Permanently' and 'Requires explicit user confirmation,' which distinguishes it from update or void operations and from sibling tools like update_time_activity and create_time_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 implies usage (when you want to permanently delete a time activity) and includes a precondition ('Requires explicit user confirmation'), but it does not explicitly compare with alternatives or state when not to use it. There is no mention of when to prefer delete over update or void, so guidance is only implied.

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