Adıma Düzenlenen Belgeleri Listele

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

No annotations provided. The description adds a note about potential instability, which is a behavioral trait. However, it does not disclose authentication requirements, pagination behavior, or error handling. The instability note is useful but insufficient for full transparency.

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, first sentence states purpose, second adds a caveat. No unnecessary words. Front-loaded and 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?

For a list tool with 13 parameters, the description covers the core function but lacks details about return format, pagination, or how filters interact. The instability note is a plus. Adequate but not complete.

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 92%, so the schema already defines parameters well. The description does not add extra meaning beyond mentioning the date range. Baseline of 3 is appropriate.

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 it lists documents issued to the user within a date range. The phrase 'adınıza düzenlenen belgeler' distinguishes it from the generic sibling 'gib_list_documents'.

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?

Implies usage for listing documents in a date range, but no explicit guidance on when to use versus alternatives like 'gib_list_documents' or when not to use. The instability note is a caveat but not a guideline.

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