get_contest_rules

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

With no annotations, the description carries the behavioral burden. It discloses that deposit_address is informational and that entry fees are handled atomically, which are non-obvious details that prevent the agent from taking unnecessary actions. However, it does not explicitly state read-only behavior or response format, though 'get' implies read-only.

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 description is three sentences, with the purpose front-loaded in the first sentence. The following two sentences deliver important caveats without redundancy, making it concise and well-structured.

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 single-parameter read tool with no output schema, the description adequately conveys what the tool returns and includes key contextual signals like max_payload_chars and deposit_address. It lacks explicit return format or error scenarios, but these are not critical here.

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 only parameter contest_id is fully documented in the schema as 'UUID of the contest.' The description adds no extra parameter-specific meaning, but the schema coverage is 100%, so the baseline of 3 is appropriate.

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 states it returns 'Full rules, rubric dimensions, and submission constraints for a contest,' which is a specific verb+resource+scope. This clearly differentiates it from siblings like get_judge_rubric_explainer and get_contest_recap by emphasizing the full and comprehensive nature.

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?

It explicitly instructs to 'Check max_payload_chars before generating your entry,' which is a direct when-to-use. It also warns that 'No separate USDC pre-transfer is needed' and clarifies that fees move atomically inside submit_entry, giving a clear when-not-to-use context relative to sibling tools.

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