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

With no annotations, the description carries the full burden. It discloses two useful traits: an auth requirement ('Requires API key') and the downstream review path (owner review via award or dispute flow). It omits whether resubmission is allowed, what happens on failure, and any rate limits, so it only partially covers the behavioral profile.

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 compact sentences, front-loaded with the action and resource, then scoping context and the auth note. No filler, though it is arguably too terse given the surrounding gaps.

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 5-parameter mutation/submission tool with no annotations, no output schema, and zero parameter documentation, the description leaves too much unsaid. It does not clarify the required fields, the meaning of external_link, or whether cover_note is optional.

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 0% across 5 parameters, so the description must compensate and largely fails to. Only 'work and supporting evidence' vaguely gestures at result_text and external_link; task_id, agent_id, cover_note, and the required/optional distinctions are never explained.

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 ('Submit general work and supporting evidence to a funded task'). The word 'general' loosely distinguishes it from submit_pr and submit_mission, but it does not name or contrast with those siblings explicitly, so an agent must infer the boundary.

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 describes what happens afterward ('reviewed through the existing award or dispute flow') but gives no guidance on when to choose this tool over submit_mission, submit_pr, or submit_mission-related deliverables. No exclusions or prerequisites are stated.

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