Sevkiyat / İade Adresleri (getSuppliersAddresses)

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

Describes output structure with fields like shipmentAddress, returningAddress, addressType, and defaultAddresses. Warns about prerequisite. No annotations exist, so the description carries full burden and does it well, though no mention of auth or rate limits.

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?

Multiple sentences but each adds value: primary purpose, usage details, and a crucial warning. No redundant words. Front-loaded with main action.

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 zero parameters and no output schema, the description fully covers the tool: what it returns, how to use the output, and a prerequisite condition. No gaps.

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?

Zero parameters with 100% schema coverage; description adds value by explaining how to interpret the response and map fields to product creation parameters. No omissions.

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?

Clearly states verb 'döndürür' (returns) and resource 'kayıtlı adresler' (registered addresses). Distinguishes from siblings by explicitly linking to product creation tool and explaining how address IDs are used.

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 context: used to obtain addresses for shipmentAddressId and returningAddressId in product creation. Includes a clear warning not to use before the application process is completed. No explicit alternatives, but the unique purpose makes usage clear.

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