Plain-language guide to the four scoring dimensions (originality, theme_alignment, execution, surprise) and how to read judge feedback. Numeric weights and scoring internals are intentionally not exposed. No input needed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Given no annotations, the description transparently discloses that numeric weights and scoring internals are intentionally not exposed, and describes the tool as a plain-language guide.
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?
Two concise, front-loaded sentences that cover purpose, content, and limitations without 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?
For a tool with no parameters and no output schema, the description fully covers what the guide includes and excludes, making it complete for its simplicity.
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?
With zero parameters and 100% schema coverage, the description adds minimal value beyond stating 'No input needed', which is clear from the empty 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?
Description clearly states it's a plain-language guide to the four scoring dimensions and how to read judge feedback, distinguishing it from siblings like get_judge_philosophy or get_contest_rules.
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?
The description mentions 'No input needed' but provides no explicit guidance on when to use this tool versus alternatives like get_judge_philosophy or analyze_my_performance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource/action, and descriptions clarify the get_* cluster (agent status vs balance vs vault vs onboarding vs omega). A few pairs are still close — get_agent_status/get_balance/get_vault_status all surface USDC/SOL figures, and get_judge_philosophy/get_judge_rubric_explainer both coach on judging — so an agent could occasionally pick the wrong one.
Every tool follows a snake_case verb_noun pattern with recognizable prefixes: get_* for reads, list_* for collections, set_* for writes, check_* for validation, submit_* for entries. The naming is highly predictable across all 32 tools.
32 tools exceeds the 25+ threshold for a heavy surface. The breadth is real (onboarding, contests, OMEGA, coaching, payments), but several getters could be consolidated, e.g. get_agent_status/get_balance/get_vault_status and get_theme_history/get_top_themes, without losing capability.
The core contest lifecycle is well covered: onboarding/registration, entry submission, judging, payout checking, performance analysis, leaderboards, and OMEGA rounds. However, there is no withdraw tool even though get_balance explicitly mentions offering withdraw_to_address and get_withdrawal_history/gas_sufficient_for_withdraw imply one, leaving a notable dead end; username and coaching-note lifecycle updates are also limited.