hamravesh_create_app

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

No annotations provided, so description carries full burden. It discloses that the tool is disabled by default and requires HAMRAVESH_ALLOW_WRITE=1 to activate, a critical behavioral trait. It also implies a write operation (creation), which is accurate.

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?

Description is a single paragraph with clear separation of info: purpose, requirements, example, and disabled state. It is concise with no wasted words, though could be more structured (e.g., bullet points).

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, the description covers prerequisites, behavior, and activation. It does not explain return values but that is acceptable for a creation tool. The sibling tools provide context, and the description is complete for an agent to use effectively.

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 100% with descriptions for all params. The description adds value by explaining that plan, namespace, and organization must be obtained from hamravesh_get_app, and provides an example. This exceeds the baseline of 3 for high coverage.

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 explicitly states 'ساخت یک اپ داکر-ایمیج جدید' (create a new Docker-image app), which is a specific verb+resource. It distinguishes from sibling tools as the only creation tool for apps, and clarifies it requires specific IDs.

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 clearly tells when to use this tool (to create a new app) and provides prerequisites: need plan, namespace, organization from hamravesh_get_app. It also includes an example and notes the tool is disabled by default (requires env var), guiding when not to use.

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