payway_docs

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

The description says 'Fetch' and 'read a specific page', which implies a read-only operation. It doesn't explicitly state there are no side effects or rate limits, but the fetch semantics and 'no credentials' note are sufficient given the simple nature of the tool.

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 concise sentences cover the purpose, usage pattern, and parameter behavior without any redundant information. The structure is clean and immediately actionable.

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 tool is simple and has no output schema. The description clearly explains what the user will get (markdown docs, index) and how to get it. No additional context is needed for correct use.

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?

The url parameter is fully described: it expects a .md URL or path from the index, and omitting it triggers the index listing. This goes beyond the schema's basic type/description, providing concrete usage details.

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 it fetches ABA PayWay developer documentation as markdown, with a distinct index-listing behavior. Sibling tools are payment operations, so this is unambiguously the documentation retrieval tool.

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?

Explains the two-step invocation pattern: omit the url for the index, then pass a URL/path to fetch a specific page. Also notes that no credentials are required, which is useful guidance.

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