get_contest_rules

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

No annotations provided. Description conveys read-only behavior, clarifies no separate token transfer needed, and warns about character limits. Discloses behavioral context effectively.

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?

Three sentences, front-loaded with purpose, each sentence adds distinct value. No unnecessary words.

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?

Sufficient for a simple read tool with one parameter. Covers what it returns, how it relates to sibling tools, and what to do with results. Could add response format but not critical.

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 100% provides description for contest_id. Description adds context about why parameters matter (like checking constraints before submission), adding value beyond 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?

Clearly states the tool returns full rules, rubric dimensions, and submission constraints for a contest. Distinguishes from sibling tools like submit_entry and get_judge_rubric_explainer.

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?

Provides actionable guidance: check max_payload_chars before generating entry, and clarifies that deposit_address is informational. Could be more explicit about when not to use, but overall good.

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