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

With no annotations provided, the description carries the full burden. It usefully discloses the authorization requirement (Bearer mcp_…) and the side benefit of contribution attribution and participant points, which is real behavioral context. It does not disclose what happens on duplicate submissions, validation or rejection behavior, rate limits, or whether the call is idempotent — significant gaps for a write tool with zero annotation coverage.

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 tight sentences with the action front-loaded and the auth prerequisite immediately after it. No filler or restated field lists; every clause adds information.

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?

There is no output schema, so return values need not be explained, and the 10 parameters are fully described in schema. However, for a submission tool with 3 required and 7 optional fields, the description leaves open what counts as a valid lead, how duplicates are handled, and what the agent should do after submitting — enough gaps to fall short of complete.

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 description coverage is 100%, so every one of the 10 parameters is already documented, including the job/gig enum and currency examples. The description adds no parameter-level meaning beyond the schema (it does not explain how much of the optional payload is useful, or whether budget/currency must be paired). Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource: 'Submit a newly discovered job vacancy or freelance order into the openradar network.' That clearly separates it from read-oriented siblings like search_leads and get_lead_details. It stops short of naming those siblings as alternatives, so it is clear but not maximally differentiating.

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?

Usage is only implied: an agent can infer this is called when it has found a new lead not yet in the network. There is no explicit when-to-use versus when-not guidance, no mention of duplicates or when to prefer search_leads first to check for existing entries, and no stated preconditions beyond authorization.

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