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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context: quests are time-bounded admin-configured campaigns, returning metric/target/reward/window fields, wallet progress when wallet_address is supplied, and a disclaimer. No contradiction with annotations.

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?

The main purpose is front-loaded and the supporting detail is compact. It uses a few dense sentences without padding or unnecessary repetition.

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 an output schema and safety annotations, the main missing piece is caller_id semantics. The description covers the core behavior and the optional wallet_address path, making it adequate but not fully complete.

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 0% description coverage, so the description must carry parameter meaning. It explains wallet_address's effect (adds progress_value and completion state) but never mentions caller_id, leaving that parameter's purpose to inference from its name alone.

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 identifies the resource as 'Crank Score quests' and notes optional wallet progress, so an agent can distinguish it from get_crank_score and other get_* siblings. It lacks an explicit verb, relying on the tool name and 'FREE read', but the intended operation is clear.

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?

No alternative tools or exclusion conditions are stated. The description implies this is for quest/progress data and explains the wallet_address condition, but it does not say when to prefer this over siblings like get_crank_score or get_leaderboard.

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