ramzinex_refresh_funds

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

No annotations provided, so description carries burden. Declares read-only effect and no fund movement, and maps to a POST endpoint. Lacks rate limit or credential failure behavior, but sufficient for basic safety.

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?

Compact description with bullet points and key details front-loaded. Includes Persian translation and endpoint path, which are relevant but not excessive.

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 one optional parameter, clear purpose, and output schema available, the description covers essential context. Explains effect, non-destructiveness, and credential requirement.

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?

Only one optional parameter 'instance' with 0% schema coverage. Description adds context: 'Configured instance to use (default when omitted).' This is minimal but adds value beyond the schema.

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?

Clearly states the verb 'refresh/recompute' and resource 'balances', with explicit read-only effect. Distinguishes from siblings like ramzinex_get_funds by noting the refresh action.

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?

Explicitly says when to use (refresh cached balances) and what it does not do (move funds). Indicates requirement for configured credentials. Could better differentiate from other balance tools, but adequate.

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