ghl_location_delete

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

Annotations already indicate destructiveHint=true; description adds irreversibility and explains the effect of the deleteTwilioAccount parameter, providing useful context beyond structured fields.

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?

Key information is front-loaded (token requirement, irreversibility). However, the description includes repeated phrases and extra details like endpoint, version, and source file, which could be trimmed for conciseness.

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?

Covers essential aspects: purpose, security, irreversibility, and key parameter behavior. For a destructive tool with no output schema, it is sufficiently complete. Could mention typical response but not critical.

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 coverage is 100% (baseline 3). The description adds meaningful context for deleteTwilioAccount (controls Twilio sub-account deletion) beyond the schema description. LocationId is simple and needs no extra explanation.

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?

Clearly states it deletes a sub-account (formerly location) from the agency and notes irreversibility. However, the description repeats 'Delete Sub-Account (Formerly Location)' multiple times, which is redundant but still clear.

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?

Explicitly requires an agency-level token and mentions OAuth scopes, setting clear preconditions. Does not explicitly mention when not to use this tool or alternatives, but the name and context imply it's for deletion only.

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