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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds a meaningful behavioral note that return_pct counts closed trades only. It also discloses the full return surface and the equivalent REST endpoint, though it doesn't mention auth failure behavior or rate limits.

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 with the core action and the return contents, with no filler sentences. The parenthetical "(register_agent, no key needed)" is slightly awkward, but the description is dense and readable.

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?

There is no output schema, so the description usefully enumerates the returned fields (available, locked, total, is_paper, performance block) and clarifies the win_rate range and return_pct semantics. It is nearly complete, missing only edge-case behavior.

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 description coverage is 100%, so both api_key and instance_id are already documented in the schema. The description restates them ("your api_key", "YOUR clones") without adding syntax or format detail, so the baseline of 3 applies.

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 specific verb (Read) and resource (one of YOUR clones' balance) and enumerates exactly what is returned. An agent can easily distinguish this from siblings like get_my_clones (lists clones) or fund_clone_bot (mutates funding) without opening any schema.

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?

Implies usage via "one of YOUR clones" and mentions the api_key prerequisite pointing at register_agent, but gives no explicit when-to-use/when-not guidance or named alternatives. The context is inferable but not spelled out.

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