apiosk_list_my_apis

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

Annotations already declare read-only, idempotent, and non-destructive behavior, and the description's 'List' is consistent. It adds useful auth context (active local wallet vs APIOSK_PRIVATE_KEY) but does not explain what happens when neither is available or how a provided wallet_id changes behavior.

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?

Single sentence with a front-loaded verb and no filler. Every word contributes to the tool's meaning.

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?

For a low-complexity read-only list with an output schema and rich annotations, purpose and auth source are covered. However, the unexplained wallet_id parameter and lack of expected behavior for missing wallet/key leave a functional gap.

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 schema has one optional wallet_id parameter with 0% description coverage, and the description never mentions it. An agent cannot determine whether wallet_id overrides the active wallet, filters results, or is needed for listing a specific wallet.

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 states a specific operation ('List') and resource ('APIs owned by the active local wallet or APIOSK_PRIVATE_KEY'). This clearly distinguishes it from single-API retrieval (apiosk_get_api) and broad discovery tools (apiosk_explore/search).

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 ownership scope implies this is for listing the caller's own APIs, but it never explicitly says when to use it versus alternatives. There is no exclusion guidance or reference to sibling tools.

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