timeiq_person_delete

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

No annotations are provided, so the description carries full burden. It only mentions the admin requirement but does not disclose whether deletion is permanent, cascading, or if any confirmation is needed. For a delete operation, more behavioral details are necessary.

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 with no fluff. It front-loads the action and resource, making it easy to parse quickly.

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 no output schema and missing annotations, the description lacks completeness. It does not explain the dry_run parameter, return value, or potential side effects. The tool list shows many related person tools, but no contextual guidance is provided.

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 has 2 parameters (slug, dry_run) with 0% description coverage. The description clarifies 'by their slug' for the slug parameter but does not mention dry_run or explain its purpose. This partial coverage leaves the agent guessing about the dry_run 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 clearly states the action ('Delete'), the resource ('team member record'), and the requirement ('by their slug (Admin only)'). It distinguishes from sibling delete tools like timeiq_client_delete.

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 explicitly notes 'Admin only', providing clear context for when the tool can be used. However, it does not specify when not to use it (e.g., preferring archive) or mention alternatives among siblings.

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