ecosystem_apply_quality_review

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

The description discloses key behavioral effects: it writes specific fields (quality_score, quality_notes, reviewed_by, reviewed_at) and clears claimed_by to allow other workers to pick up the next row. With no annotations provided, this provides sufficient transparency for a simple update operation.

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?

The description is two sentences with no unnecessary words. The first sentence states the high-level purpose, and the second provides specific details about the fields and lock release. Every sentence adds value.

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?

Given there is an output schema (context indicates present), the description does not need to explain return values. It covers the essential behavioral effects and side effects. It does not mention error conditions or idempotency, but for a straightforward update tool, it is largely 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 baseline is 3. The description mentions some fields (quality_score, quality_notes) that are parameters, but adds minimal additional meaning beyond the schema. It also mentions reviewed_by and reviewed_at, which are not input parameters, potentially causing confusion.

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 clearly states 'Submit quality review result and release the claim lock', which specifies the verb (submit/release) and the resource (quality review/claim lock). It distinguishes from siblings like ecosystem_claim_review (which claims) and ecosystem_release_claim (which only releases) by combining both actions.

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?

While the description implies the tool is used after a review is completed and to release the lock, it does not explicitly state when to use it versus alternatives (e.g., using ecosystem_release_claim instead if no review submission is needed) or mention any prerequisites or conditions.

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