bitflow_get_keeper_contract

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

With no annotations, the description does carry real operational context: public endpoints, ~500 req/min, no API key, mainnet only. However, for a tool that can CREATE an on-chain construct, it says nothing about what creation does (funding, ownership, reversibility, whether it is idempotent) or what authorization is needed.

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?

Front-loaded purpose followed by short scoped notes; each sentence adds a distinct constraint. The closing 'Tip' promoting earning_opportunities is marginally tangential but brief.

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?

No output schema exists, so the description should clarify what is returned in each mode (created contract vs existing contract), and it does not. Rate-limit and network constraints are covered, but the mutation semantics for the 'create' path remain a 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?

Schema coverage is 100% and the single stacksAddress parameter is fully documented there, including the wallet fallback, so the baseline of 3 applies. The description adds no additional 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?

States a concrete verb+resource ('Get or create a Bitflow Keeper contract') and explains the resource's purpose (scheduled/automated token swaps). It distinguishes itself from quote/swap siblings, but the dual get-or-create behavior and the near-named sibling bitflow_get_keeper_user are not distinguished.

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?

Usage is implied through 'automated swaps' and the mainnet-only note, plus a pointer to earning_opportunities. It never says when to use this versus bitflow_get_keeper_user, bitflow_create_order, or bitflow_swap, and it doesn't say when creation occurs versus retrieval.

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