hamravesh_set_app_enabled

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

Discloses that the tool is disabled by default and requires an env var, and mentions a dry_run mode. However, no details on side effects, errors, or what 'disabled' means. With no annotations, more is expected.

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 includes cryptic parentheses notes. It could be more clear and structured. Not excessively long, but not optimally written.

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?

With no output schema and minimal description, the agent lacks information about return values, effect of enabled parameter, and the optional org. The tool is incomplete for correct invocation.

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 0%, and the description does not explain any of the three parameters (app_id, enabled, org). It adds no value beyond the schema.

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 it turns an app on/off, using the verb 'set' in the name and Farsi description. It is distinct from sibling tools like restart or redeploy. However, the extra notes about dry_run and env var may distract.

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 versus alternatives. The only hint is the note about HAMRAVESH_ALLOW_WRITE being required, but no when-not or comparison with siblings.

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