alonomic_get_me

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

No annotations provided, so description takes full burden. Declares read-only, implicit login, endpoint mapping, and return fields. Lacks error handling or rate limits but sufficient for a simple retrieval.

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?

Very concise: two lines of English, Persian translation, endpoint, return fields, and parameter explanation. No redundant words.

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?

With output schema present, description covers all needed: purpose, usage, parameter, return values. Complete for a simple read-only tool.

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 has one parameter 'instance' with no description. The description adds 'Configured instance to use (default when omitted)', clarifying its purpose and optionality. Schema coverage 0% makes this addition valuable.

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 'Get the Alonomic business account profile and credit (read-only)'. Provides Persian translation and endpoint mapping, leaving no ambiguity. Distinct from sibling tools like alonomic_login.

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?

Mentions 'Logs in implicitly if needed', giving context on when to call. However, no explicit when-not-to-use or comparison to alternatives beyond the read-only nature.

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