pod_install

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

With no annotations, the description carries the full burden of disclosing side effects. It only states that the command runs, omitting that it modifies Podfile.lock and the Pods directory, may require network access, or could fail if CocoaPods is missing. This significant gap in mutation behavior reduces transparency.

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, focused sentence that states the command and its purpose. There is no redundant or irrelevant information, making it highly concise and well-structured.

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 is simple with three self-documenting boolean parameters, but the missing annotation coverage and lack of side-effect disclosure leave the description incomplete. It does not mention what changes occur or prerequisites, though the simplicity of the tool mitigates this somewhat.

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%, with each parameter (verbose, repoUpdate, cleanInstall) already having descriptive text. The tool description adds nothing about parameter behavior or syntax, so the baseline of 3 applies.

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 specifies the action ('Runs pod install') and the resource ('in the active project directory to install CocoaPods dependencies'). This distinguishes it from sibling tools like pod_update and pod_repo_update by focusing on the install action.

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 implicitly suggests use when installing dependencies in the active project directory, but it does not explicitly compare to alternatives such as pod_update or pod_init, nor does it mention when not to use it. The context is clear but lacks explicit guidance.

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