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

Annotations already cover read-only and open-world. The description adds real value beyond them: the id-space semantics, the fact that the response echoes both ids, and the critical network caveat that this is Base Sepolia testnet with no monetary value. No return-format details, but annotations lighten the load.

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 is good, but the network disclaimer is a multi-sentence tangent. Every sentence earns its place conceptually, yet the network block could be tighter and it dilutes the flow.

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 a 2-param read tool with no output schema, the description covers the tricky id-space semantics and testnet context well. Only minor gaps remain around what the round/winner payload looks like.

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%, so the schema documents week and idSpace fully. The description reinforces the id-space danger but doesn't add new syntax or format meaning beyond what's in 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: read one draw's five rounds and its winner. The scope (single draw, rounds + winner) clearly distinguishes it from siblings like luckdrop_get_draw or luckdrop_check_prize.

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?

Explicitly tells the agent when to pass idSpace='contract' (when following contractWeekId from the chain) and warns that omitting it yields a wrong-but-valid-looking result. This routing guidance is unusually concrete.

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