ibmcloud_cf_push

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

No annotations are provided, so the description must disclose side effects. It merely says 'Deploy' without noting that this may create or update an app, upload code, require a targeted CF space, or affect running instances.

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 sentence with no redundancy. It's front-loaded and to the point, though it might be too sparse for completeness.

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 deployment command with 7 parameters and no annotations, the description is inadequate. It lacks information about deployment behavior, prerequisites, return values, or post-conditions. The rich sibling list hints at a complex environment but the description doesn't orient the agent.

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?

All 7 parameters have schema descriptions (100% coverage), so the description doesn't need to repeat them. It adds no additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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?

States the action clearly: 'Deploy a Cloud Foundry application' – a specific verb+resource. Though it doesn't elaborate on deployment specifics, it's distinguishable from sibling tools like listing apps (ibmcloud_cf_apps) or starting an app (ibmcloud_cf_start).

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 context, prerequisites, or alternatives are mentioned. The description gives no indication of when to prefer this over other CF commands like ibmcloud_cf_start or ibmcloud_cf_app.

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