Referans Verileri

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

No annotations are provided, so the description carries the full burden. It describes the tool as returning lists but does not disclose behavioral traits such as read-only nature, authentication requirements, or performance characteristics. For a simple lookup tool, this is adequate but not rich.

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 a single sentence listing the reference data types. No redundant information, every word serves a purpose.

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 low complexity (one parameter, no output schema), the description covers the essential purpose. However, it could specify that the output is a list of code-value pairs or similar structure. The absence of output schema details is a minor gap.

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 compensate. It adds context by mentioning that this data is used 'during document creation', which goes beyond the enum list. However, it omits one enum value ('belge_turleri') from the listing, slightly reducing completeness.

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 it returns reference lists (constant lists) used in document creation. The verb 'returns' and resource 'sabit listeler' (constant lists) are specific, and the listed items (birimler, vergiler, etc.) distinguish it from sibling tools that handle document creation, deletion, or authentication.

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?

The description implies usage during document creation to obtain reference data. It does not explicitly state when not to use or mention alternatives, but the context is clear given the sibling tools are for different actions (e.g., creating invoices, deletion).

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