apiosk_help

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

The annotations already establish that this is a non-destructive read-only call, and the description is consistent. It adds a useful outline of the returned explanation content but does not disclose deeper behavior such as whether the help is static, rate-limited, or dependent on auth state.

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 a single front-loaded sentence with listing but no redundancy. It efficiently enumerates what the tool explains, though the long list of topics makes it slightly dense.

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 the optional single parameter, the schema's enum documentation, and the presence of an output schema, the description is mosely sufficient for a help tool. The main gap is its relationship to closely related sibling help tools, which context does not clarify.

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 for the single optional 'topic' parameter is 100%, and the enum values are self-descriptive, so the description does not need to add much. It provides a light mapping of topics (auth, payments, workflow) but relies on the schema for detailed parameter meaning.

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's job with a verb ('Explain') and a distinct resource (Apiosk MCP), listing specific areas: connection, auth, USDC/x402 payments, and workflow. It does not explicitly differentiate from overlapping siblings like apiosk_get_started or apiosk_payment_guide, so it falls short of a 5.

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?

The description implies the tool is a general help/educational entry point, but it never states when to prefer it over sibling tools. The schema's topic enum partially compensates by directing the agent to use 'discovery' and 'rails' for specific learning goals, so there is some contextual guidance.

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