Revoke A Person'S Login

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

Beyond annotations (destructiveHint: true), the description adds key behavioral details: the action cannot be undone, the person remains as an assignable resource, and Resource Planning records are permanently deleted. This helps the agent understand side effects.

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 reasonably concise but contains redundancy ('This cannot be undone' twice) and includes API endpoint details that may not be essential for agent understanding. Slightly verbose for the information provided.

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?

The description covers the main action and side effects but lacks clarification on what constitutes 'Resource Planning records' and what the response looks like. Given the destructive nature and no output schema, more context would be beneficial.

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 100%, so the schema already documents both parameters. The description merely states 'Required parameters: company_id, person_id' without adding new meaning, meeting the baseline.

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 revokes a person's login while keeping them as assignable, differentiating it from siblings like 'enable_a_person_to_log_in'. However, it introduces ambiguity by also mentioning 'permanently delete the specified Resource Planning records', which may confuse the primary purpose.

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 does not provide explicit guidance on when or when not to use this tool compared to alternatives. While it states the action and irreversibility, it lacks context for decision-making among related tools.

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