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

Annotations already declare the mutation, idempotency, open-world, and non-destructive profile. The description adds value beyond them by warning against including credentials and clarifying retry semantics tied to the idempotency key, though it says nothing about what a successful submission returns or rate limits.

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?

Three short sentences, front-loaded with purpose followed by the two key constraints. Every sentence carries operational value with no repetition or filler.

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 four-parameter mutation tool with no output schema, the description plus rich annotations cover the safety and retry picture an agent needs. Minor gaps remain around the category values and expected outcome, but the core call path is well specified.

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 coverage is 25%, so the description must compensate, but it only implicitly illuminates idempotencyKey behavior. It offers no guidance on the category enum values or the message content/length constraints beyond the schema's own bounds.

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?

States a specific verb (submit) and resource (bug report, idea, or other feedback) scoped to the authenticated member, which cleanly distinguishes it from the read-only sibling springroll.feedback.list. An agent can identify the tool's operation without opening the schema.

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?

Gives actionable context: exclude credentials and reuse the idempotency key when retrying the same submission. It does not name the complementary sibling (feedback.list) or state explicit when-not conditions, so it falls short of full routing guidance.

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