e-Müstahsil Makbuzu Oluştur

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

No annotations provided. The description adds one behavioral trait: 'GV stopajı ve toplamlar otomatik hesaplanır' (automatic calculation of withholding tax and totals). However, it omits other key behaviors such as whether it creates a draft (taslak) meaning it's non-destructive, authorization requirements, or side effects. The description carries the full burden but only partially addresses it.

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?

Two sentences, front-loaded with purpose and a key behavioral feature. No wasted words. Efficient for quick understanding.

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 12 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, prerequisites, or how the tool fits with other draft creation tools. The automatic calculation hint is helpful but not enough for a complex tool.

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 low (25%, 3 of 12 parameters have descriptions). The description mentions auto-calculation of taxes, which indirectly clarifies that certain tax-related parameters (e.g., gvStopajOrani) may be optional, but it does not map to specific parameters or add meaning beyond the schema. It provides minimal additional value.

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 it creates a draft 'e-Müstahsil makbuzu' (producer receipt) on GİB e-Arşiv portal, which is distinct from sibling tools like 'gib_create_invoice' and 'gib_create_self_employed_receipt'. The verb 'oluşturur' and resource specification are clear.

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. It does not mention prerequisites, exclusions, or comparative context. The usage is only implied by the tool name and title.

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