Akakçe account info

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the operation is a read ('döndürür') and authentication is required. It does not mention behavior when unauthenticated (error vs. empty) or any caching/refresh semantics.

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 short sentences: the return content is front-loaded, with the auth prerequisite appended as a trailing constraint. No filler.

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?

No output schema exists, so the description's field enumeration (name, email, city/district, notification count) does real work in telling the agent what comes back. Slightly incomplete in that it doesn't specify the failure mode when not logged in.

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?

Zero parameters, so there is nothing to disambiguate and the baseline is 4. The schema is empty and fully described, so the description loses nothing by omitting parameter detail.

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?

States a specific verb (döndürür/returns) and resource (logged-in user's profile info), and enumerates the returned fields (name, email, city/district, notification count). This makes it clearly distinct from siblings like akakce_login and akakce_notifications, though it never explicitly names an alternative.

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 clause 'Giriş gerektirir' (requires login) gives an important precondition for calling it. However, there is no guidance on when to prefer this over siblings such as akakce_login (to establish the session) or akakce_notifications (for notification content).

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