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

With annotations all false, the description carries the burden and delivers: it explicitly discloses idempotency ('one submission per team, and calling again overwrites it') and the lock/freeze behavior with a 'locked' return. It also states required scope and team membership, plus the return shape. 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?

Four dense sentences, each adding distinct value: idempotency, rubric guidance, lock behavior, and args/returns/scope. The use of backticks and a compact Args/Returns block keeps it scannable with no filler.

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 7-param tool with no output schema and sparse annotations, the description is thorough: return shape, lock behavior, idempotency, scope, and the key scoring field guidance. It doesn't enumerate all error cases, but the essentials are covered.

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 description adds meaningful guidance to agent_surface — explaining it is what the rubric scores and listing example content (MCP server, A2A, agent payments) — and clarifies folder_id as a vault folder with slides/video. However, it merely lists eid, title, repo_url, and demo_url without elaboration, and schema coverage is only 43%, so it only partially compensates.

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 opens with 'Submit (or re-submit) your team's project' — a specific verb and resource. It clearly differentiates from sibling hackathon tools by explaining idempotency and overwrite semantics, making the tool's unique purpose unmistakable.

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 states when to use: for submitting or re-submitting, even quoting the pragmatic scenario of fixing a demo link at 2:55. It also gives a clear exclusion: once the organizer locks submissions, the record freezes and further calls return 'locked'. It doesn't name specific sibling alternatives, but the context is sufficient.

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