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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context beyond them: it requires the caller's own CabalSpy API key with a CabalSpy ID instance and explicitly says demo accounts will not work. It also discloses that results are cursor-paginated via next_cursor and that each thesis carries the author's live position (holding/sold, invested, PnL).

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-loads the purpose and return shape, then layers usage examples, the auth prerequisite, and the pagination instruction. Mostly economical, though the example call and the 'Page with the returned next_cursor' line could be tightened.

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 an 8-parameter read tool with a full output schema and read-only/open-world annotations, the description covers the remaining agent-facing gaps: the auth prerequisite, the pagination loop, and what a returned thesis contains. Nothing needed to invoke it correctly is missing.

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 blockchain, mint, sort, scope, stance, cursor, instance and limit are already documented at the field level. The description only echoes an example blockchain/mint pair and repeats the sort choice as 'latest (or top)', adding no syntax or semantics beyond the schema.

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 and resource ('What do verified holders think about a token?') and names the exact payload: a bull/bear summary plus latest or top theses. It further defines a 'thesis' as a short post only holders of the token in a verified wallet can write, which cleanly separates it from siblings like csid_thesis or csid_latest_theses.

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?

Gives concrete usage triggers ('What do holders say about $BONK?', 'Is sentiment on this token bullish?') so an agent can map a natural-language sentiment question onto this tool. It does not, however, state when to prefer the neighboring csid_latest_theses or csid_user_theses, or name any exclusion.

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