mobileci_add_deployment

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

With no annotations, the description carries the full burden for behavioral disclosure. It only reveals that this is a Pro feature, but doesn't say whether it writes files, requires an existing mobile CI setup, how api_key is used, or what the generated pipeline looks like. 'Generate' implies output, but side effects and prerequisites are unstated.

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?

A single, focused sentence with no filler; the key action and Pro gating are front-loaded. It is efficient, though slightly too terse for a tool with two parameters and no other documentation.

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?

For a generation tool with no output schema and no annotations, this description is insufficient. An agent cannot tell what artifacts are created, what api_key is for, or what being a Pro feature means for invocation. Important call details are missing.

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 50%: 'directory' has a schema description, but 'api_key' has none. The description does not compensate by explaining api_key's role or how directory should be provided. Since one parameter is entirely undocumented and the description adds no parameter meaning, this falls below baseline utility.

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 names a specific verb and resource: 'Generate app store deployment pipeline'. The parenthetical '(Pro feature)' adds useful gating context. It doesn't explicitly differentiate from siblings like mobileci_setup_fastlane or mobileci_add_signing, but the core resource is 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 choose this tool over mobileci_setup_fastlane, mobileci_add_signing, or other deployment-related siblings. There are no prerequisites, exclusions, or alternative conditions. The agent must infer the appropriate use case.

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