uninstall_agent_marketplace_action

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

The tool has no annotations, so the description must convey behavior on its own. It only states the action without discussing side effects, reversibility, or impacts on the company or marketplace. No mention of whether uninstallation requires confirmation or what happens to associated data.

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, concise sentence with no extraneous information. It is well-structured and easy to read.

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 the tool's apparent complexity (idempotency, installation context), the description is very sparse. It does not explain what an 'action' is, how the selected company is determined, or what the idempotency_key is for. The sibling tools suggest a broader workflow, but the description lacks integration context.

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 schema defines three parameters, but none have descriptions. The description does not explain the meaning of installation_id, idempotency_key, or reason. Parameters are only self-explanatory by name, and it's unclear how to obtain installation_id.

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: uninstalling an action from the selected company. The verb 'uninstall' distinguishes it from installation, activation, and other related operations. However, it does not explicitly contrast with sibling tools like activate or archive, and 'selected company' relies on external context.

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?

No usage guidance is provided beyond the one-line description. There is no mention of when to prefer this tool over alternatives or what prerequisites are needed (e.g., an existing installation). The description fails to explain the circumstances under which uninstallation is appropriate.

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