hamravesh_redeploy_app

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

With no annotations, the description adds behavioral context: the tool is disabled by default, requires HAMRAVESH_ALLOW_WRITE=1, and supports a dry-run mode. However, it lacks details on whether the redeploy is destructive, reversible, or has side effects.

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 short but packs multiple pieces of information (purpose, disabled status, activation instruction, dry run). It could be better structured, but it is not excessively long.

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 no output schema and no annotations, the description fails to cover prerequisites, return values, error conditions, or parameter details. It is minimally adequate for a simple redeploy tool but missing essential 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?

Schema coverage is 0%, but the description does not explain the parameters (app_id, org). It only mentions the high-level operation, leaving the agent to guess parameter meanings.

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 'redeploy app from latest commit/build', specifying the verb (redeploy) and resource (app). However, the note about being disabled and requiring activation introduces some ambiguity about its current usability.

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 explicit guidance on when to use this tool vs alternatives like hamravesh_restart_app. The dry run and activation notes are provided but do not contextualize appropriate usage scenarios.

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