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

With no annotations, the description carries the full burden of disclosure. It reveals that the tool runs endpoint checks before submitting, returns specific problems instead of filing a rejected item, opens a public GitHub issue, and that there is no revise-and-resubmit or appeal. This thoroughly exposes the mutation behavior, public visibility, and irreversibility.

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 efficiently concise: three sentences, each adding value. It front-loads the core action ('Submit a finished piece') and then provides crucial behavioral details without redundancy. No wasted words or irrelevant 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?

Given the tool's complexity (10 parameters, no output schema, no annotations), the description covers the essential workflow: checks, problem reporting, public issue creation, and lack of appeal. It does not fully detail the success response, but the description of the outcome (comment on the issue) provides adequate context for an agent to understand the result.

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 60%, so the schema already explains most properties. The tool description does not add parameter-specific details beyond the schema, nor does it compensate for the 40% missing coverage. However, it does clarify the overall validation behavior that affects parameters like confirm_invented_citations, keeping it at baseline 3.

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 the tool's function: 'Submit a finished piece for review.' It also distinguishes itself from a generic submit by noting it runs format checks first and returns specific problems. This differentiates it from siblings like get_guidelines and get_recent_issues, which handle retrieval rather than submission.

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 provides clear context: this tool is for submitting a finished, format-checked piece. It implies that the tool is not for drafting or retrieving guidelines, but it does not explicitly name alternatives or when-not-to-use. Since the sibling tools are not referenced, the guidance is implicit rather than explicit, making 4 appropriate.

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