pin_agent_marketplace_action

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

There are no annotations to signal side effects, and the description does not disclose whether pinning is idempotent, reversible, or what happens if the expected revision does not match. The 'compare-and-set' implies an atomic conditional update, but this is not explicitly explained.

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, tightly worded sentence that conveys the core action and key qualifier without extraneous detail.

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 tool has an output schema, but the description provides no information about return values, error conditions, or concurrency behavior. Given the complexity of compare-and-set, more detail is needed for correct invocation.

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 description indirectly maps 'installation' to installation_id, 'revision' to revision_id, and 'compare-and-set' to expected_revision_id, but leaves idempotency_key unexplained. Parameter names are self-explanatory, but the description adds only partial context for the optional compare-and-set semantics.

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 verb 'pin' clearly identifies the action on an 'installation,' and the mention of 'immutable revision' and 'optional compare-and-set' specifies the key behavior. It does not explicitly distinguish from sibling actions like activate or install, but the unique verb makes the purpose 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?

No guidance is provided on when to use this tool versus alternatives such as install, activate, or archive. The description does not state prerequisites, conditions for using compare-and-set, or any exclusions.

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