Düzenlenen Belgeleri Listele

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

No annotations exist; description adds that results include both draft and signed documents, and lists filter options. However, it doesn't disclose pagination behavior, response format, or authentication needs.

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 clear, front-loaded sentences with no redundant information. Every word adds value.

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 13 parameters and no output schema, the description covers core purpose and filters. Lacks mention of pagination (limit/offset) and sorting (sortAsc), but schema provides those details.

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 coverage is 92%, so baseline 3. The description lists filter categories but does not add meaning beyond schema descriptions (e.g., date format, enum values).

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 uses a specific verb ('listeler' - lists) and resource ('belgeleri' - documents), and distinguishes from siblings (e.g., gib_list_documents_issued_to_me) by focusing on documents edited in date range.

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 vs alternatives like gib_get_document or gib_list_documents_issued_to_me. No mention of prerequisites or exclusions.

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