Referans Verileri

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

No annotations provided, but description discloses that the tool returns fixed lists and describes contents (e.g., settlement fields). Does not mention destructive actions or auth needs, acceptable for read-only tool.

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 covering main content. Front-loaded with list of returned types. Could be more structured (e.g., bullet points) but overall efficient.

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, description provides good overview of each reference data type and links to alternative tool. Sufficient for agent to decide and invoke correctly.

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 has 1 enum parameter with 0% description coverage. Description compensates by explaining what each kind of reference data contains (e.g., 'settlement_islem_turleri gives description, effect, signs').

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?

Description clearly states 'Returns fixed lists' and enumerates specific reference data types (return reasons, statuses, cargo companies, etc.), contrasting with sibling trendyol_get_claim_issue_reasons for rejection reasons.

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?

Explicitly tells when to use the tool (to get reference data) and when to use an alternative (trendyol_get_claim_issue_reasons for full rejection reasons). Could be improved with more general when-not-to-use guidance.

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