alopeyk_print_invoice_url

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

With no annotations, the description carries the full burden. It clearly states 'no network call' (safe read operation) and that it returns a URL. No side effects mentioned, but for a simple URL builder, this is sufficient.

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 concise with an Args section, but includes a redundant Persian phrase. Still, every sentence serves a purpose and it is front-loaded.

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 annotations and minimal schema, the description covers the tool's core behavior (URL building, no network call) and parameters. Output schema exists, so return value explanation is not needed. Adequate for a simple 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 0%, so the description must explain parameters. It does so minimally: 'order_id: Numeric id' and 'instance: base URL'. Adds meaning beyond the schema's titles but could be more detailed (e.g., token source).

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's verb ('Build') and resource ('printable invoice URL'), and distinguishes it from siblings like 'alopeyk_tracking_url' by specifying it's for invoices. The Persian purpose adds clarity.

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 or when not to use it. The description only mentions 'no network call', but does not compare to other URL-building or order-related tools.

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