hamravesh_scale_app

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

With no annotations, the description carries full weight. It discloses the tool's disabled status, the need for an activation environment variable, and the dry-run preview option, providing critical behavioral context beyond the input schema.

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 brief (two sentences) but packs essential caveats. It is front-loaded with the primary action, though the mix of Persian and English and the use of parentheses for the notes could be slightly clearer.

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 simple write tool with no output schema, the description covers the core purpose, activation requirement, and preview mode. However, the lack of parameter documentation leaves gaps, making it only moderately complete.

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 does not explain any of the three parameters (app_id, replicas, org). Schema coverage is 0%, so the description should compensate, but it only vaguely describes the overall action without parameter details.

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 the tool changes the replica count of an app, using a specific verb and resource. It is distinct from sibling tools like restart, redeploy, etc., which focus on other app lifecycle operations.

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 explicitly notes the tool is disabled by default and requires setting HAMRAVESH_ALLOW_WRITE=1 to activate, and mentions a preview mode with dry_run. However, it does not provide alternatives or contraindications among siblings.

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