hamravesh_create_saas

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

With no annotations, the description must cover behavioral traits. It discloses that the tool is disabled by default (requires env variable), the HTTP method (POST), and dry_run support. However, it does not mention permissions needed, idempotency, throttling, or whether the operation is destructive. Mutation is implied but not explicitly stated.

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 moderately concise but includes extraneous details such as the full endpoint URL and debug flags. It could be streamlined to focus on essential usage instructions without technical internals. The mixed Persian/English may hinder clarity for non-Persian speakers.

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 the complexity (nested object body, no output schema), the description adequately explains the workflow (list products first) and dry_run. However, it does not describe the return value or error scenarios, leaving gaps for an agent to understand what response to expect.

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?

Description adds meaningful context beyond the schema: explains that 'body' must contain product-specific fields from listing products, and describes 'dry_run' as preview-only. However, 'org' parameter is not explained, and schema coverage is 67%—the description compensates for the omitted parameter by focusing on the critical ones.

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 creates a marketplace SaaS service (e.g., GitLab Runner, WordPress) and distinguishes from sibling tools like hamravesh_get_saas or hamravesh_list_saas. However, it does not explicitly differentiate from other create tools (e.g., hamravesh_create_app), though the mention of 'marketplace' provides implicit distinction.

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?

Provides explicit step-by-step guidance: first use hamravesh_list_marketplace_products to inspect product fields, then pass the complete body. Also mentions dry_run capability. Does not specify when to avoid using this tool or alternatives for non-marketplace resources.

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