GİB Girişi

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

With no annotations, the description must fully disclose behavioral traits. It explains the login and token acquisition, and the special test mode behavior. However, it does not mention potential side effects (e.g., whether previous sessions are invalidated), rate limits, or token expiration, which would be important for an agent managing sessions.

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 two sentences, front-loaded with the primary action, and contains no extraneous information. Each sentence adds value: the first states the core function, the second clarifies parameter behavior and credential sourcing.

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 and no annotations, the description adequately covers purpose, parameters, and credential sourcing. However, it lacks information about the return value (the token format or usage), which would be useful for an agent to chain subsequent calls. The description is sufficient for a straightforward login tool but leaves some 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?

The schema has 100% coverage of parameter descriptions, but the description adds significant meaning beyond the schema. It explains the interplay between testMode and username for automatic test account creation ('testMode=true ve kullanıcı adı verilmezse otomatik olarak yeni bir test hesabı alınır'), and provides guidance on obtaining credentials, which the schema does not include.

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 the tool logs into the GİB e-Archive portal and obtains a session token ('GİB e-Arşiv portala giriş yapar ve oturum tokenı alır'). This is a specific verb-resource pair that distinguishes it from all sibling tools, which are other operations like creating invoices or listing 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?

The description provides guidance on when to use testMode and auto-account creation ('testMode=true ve kullanıcı adı verilmezse otomatik olarak yeni bir test hesabı alınır') and advises where to obtain real credentials. It does not explicitly state when not to use the tool or compare to alternatives, but the context of login versus other operations is clear.

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