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

Annotations already mark this as a non-destructive, non-read-only write. The description adds value beyond them: a rate limit ('Max 5 requests/hour') and a privacy/consent rule for the email field. It does not describe the response or what happens after a request is recorded, keeping it from a 5.

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 tight sentences, front-loaded with the core action, then inputs, then the email caveat and rate limit. Every sentence earns its place with no padding.

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?

No output schema and all parameters optional, so the description is the main guidance. It covers the mutation's privacy, consent, and rate-limit constraints well, but leaves agent_name and notify semantics unexplained.

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 0%, so the description carries the burden. It explains topics, idea, tier, and the email/notify pairing, but omits agent_name and never clarifies the notify boolean directly. It covers most but not all six parameters.

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 names a specific verb and resource: submitting a request for a new kit to Agent Field Kit. It is clear the tool captures demand for future kits, which distinguishes it from the sibling vote_agent_poll, though it does not explicitly name that sibling.

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 gives input guidance ('Pick topics and/or describe an idea; optional price tier') which implies when to use it. However, there is no explicit when-to-use versus alternatives guidance, and the relationship to vote_agent_poll (also a signal/feedback tool) is left for the agent to infer.

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