ramzinex_authenticate

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

With no annotations, description fully discloses behavior: caches token in memory, never returns token, uses POST endpoint, returns success/error structure. Does not mention side effects beyond caching, but adequate for non-destructive auth.

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?

Structure is clear: English summary, Persian purpose, then details, Args, Returns. Front-loaded main purpose. Persian adds length but may aid multilingual agents. Overall concise.

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 single optional parameter and output schema mentioned in description, the description covers return shape and caching behavior. Lacks error detail but sufficient for simple auth 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 description coverage is 0%, so description adds value by explaining 'instance' parameter and default. However, lacks cross-reference to list_instances or details on valid instance 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?

Description clearly states 'Authenticate an instance and cache its bearer token' with specific verb and resource. Includes Persian purpose for clarity. Sibling tools are all functional operations, making this the only authentication tool, so no confusion.

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 before private calls but does not explicitly state 'call this first' or provide alternatives. Describes two authentication methods (api_key vs api_token) but no exclusions or when-not-to-use.

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