arvan_docs_fetch

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

Annotations do not contradict the description. The description adds the allowed domain restriction. However, it does not disclose potential side effects, authentication needs, or error handling beyond the constraint.

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 concise with two sentences, no redundant information, and easy to parse.

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?

The description covers the main function and output format. However, it lacks details on error scenarios, rate limits, or how to handle invalid URLs, which could be useful for a fetch operation.

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 coverage is 0%, and the description does not explain the `url` or `max_chars` parameters. The agent receives no guidance on URL format or the behavior of max_chars.

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 fetches an ArvanCloud documentation page and returns plain text. It specifies allowed domains, distinguishing it from sibling tools like arvan_docs_search and arvan_docs_topics.

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?

No guidance on when to use this tool versus alternatives like arvan_docs_search or arvan_docs_topics. Only a domain constraint is provided, but no context for decision-making.

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