ghl_marketplace_uninstall_application

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

Description confirms destructive behavior (removes access, stops functionality) consistent with annotations. Adds OAuth scope detail. No contradictions.

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 sentences plus endpoint and scopes; front-loaded with action and effect, no wasted words.

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?

Provides all needed information for a simple destructive operation, including auth scopes and parameter roles, given no output schema.

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 already covers all 2 parameters with descriptions; description adds value by noting that 'reason' is required for developer uninstalls, beyond what schema states.

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 'Uninstall an application' and explains that it removes access and stops functionality, distinguishing it from other marketplace tools like charge-related ones.

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?

Provides context on company vs location scoping but lacks explicit guidance on when to use this tool versus other marketplace tools or when not to use it.

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