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

No annotations are provided, so the description carries the full burden. It states the action (submit) and a prerequisite (job_id) but does not disclose consequences such as irreversibility, side effects, or what happens on success/failure. For a mutation tool, this is a significant gap.

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 extremely concise, using two short phrases that immediately convey the action and prerequisite. No redundant words, and the key information is front-loaded.

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?

The tool is simple with one fully documented parameter, but the description lacks information about return values or what happens after submission. Given no annotations and no output schema, a bit more context about the result or side effects would make it more complete, but it's adequate for basic selection and invocation.

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?

The input schema already provides full coverage for jobId ('job_id aus brief_create_checkout.'). The description repeats this information in prose ('Braucht die job_id aus brief_create_checkout') without adding new semantic detail, format, or constraints. Baseline of 3 is appropriate.

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 action: 'Nach Zahlung: Brief einreichen' (submit the brief after payment). It distinguishes from siblings like brief_create_checkout and brief_status by specifying the post-payment submission step. The verb 'einreichen' and resource 'Brief' are specific.

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 specifies when to use the tool: after payment ('Nach Zahlung'). It also references the required prerequisite, the job_id from brief_create_checkout, which provides contextual sequencing relative to a sibling tool. However, it doesn't explicitly state when not to use it or name alternative tools for different scenarios.

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