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

Annotations cover safety hints (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the description correctly does not contradict them. It adds valuable context beyond annotations: returns a submission_id, publication is gated on review, key claims need evidence, duplicates/rate limits cause errors with a code, and an API key is required.

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 tight sentences, front-loaded with the core purpose, followed by return value, validation rule, failure modes, and auth requirement. Every sentence adds information without redundancy.

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 nine-parameter submission tool with no output schema, the description covers return value, review gating, evidence requirement, error behavior, and auth. It is fairly complete, though it could briefly mention parameter expectations or the review workflow timing.

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 only 33%, and the description does not enumerate or clarify the nine parameters. It adds only the high-level expectation that every key claim needs evidence, which partially compensates but leaves required parameters like author_confidence, event_time, and expires_at unexplained in both schema and description.

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 a specific verb+resource: 'Submit a news article for editorial review.' It clearly distinguishes this tool from read-oriented siblings like get_feed, get_article, and get_submission, and from revise_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?

It implies usage by describing editorial review and consequences like refusal for duplicates or rate limits, but does not explicitly state when to choose this over revise_submission or how to handle a refused submission. No alternatives or exclusions are named.

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