How to get a cogDepot account

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

The description adds non-obvious behaviors not covered by annotations: requires no API key, spends no credits, returns instructions, and does not create accounts or send requests. These complement the readOnly and idempotent hints without contradiction.

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?

Every sentence delivers unique value: purpose, usage triggers, coverage, return behavior, and exclusions. Front-loaded with the core purpose, and no filler or redundancy.

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 no output schema, the description explicitly states it returns instructions for a human/agent to follow. It also discloses the lack of side effects (no account creation, no requests), making the tool's context fully understandable.

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?

There are zero parameters; the tool's behavior is fully explained without needing parameter details. The description covers what the tool does and its scope (three ways to get a key), which suffices given no input parameters.

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 purpose: explaining how to obtain a cogDepot API key and become able to trade. It explicitly differentiates from siblings by defining when to call it (no account, missing/unfunded key) and what it does not do (create account, send requests).

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?

Provides explicit when-to-use guidance (when user lacks account or key is missing/unfunded) and when-not-to-use (does not create account or send requests). It also names alternatives implicitly through context, making the guidance complete.

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