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

The annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false. Beyond those, the description adds the genuinely useful behavioral fact that a human reads submissions and no response is sent, which the agent cannot infer from annotations. It omits other relevant traits such as who may submit, any rate limits, or what happens on retry.

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?

Two short sentences with zero filler, function stated first and the expectation-setting caveat second. Nothing could be removed without losing meaning.

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 7-parameter tool with a nested context object and no output schema, the description is adequate but thin: it conveys purpose and the no-reply contract but leaves the richer optional fields (severity, request_id, idempotency_key) entirely to the schema. An agent can call it correctly with just a message, so the gap is not severe.

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?

With 7 parameters and only 57% schema description coverage, the schema does most of the work and the description compensates only slightly — the bug/idea examples loosely point at the category enum. It says nothing about severity, context, endpoint, request_id, or the idempotency_key retry convention, leaving the agent to read the schema for all of those.

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?

"Tell the SimianX team about a bug, missing data or an idea" gives a specific verb (tell/report) and recipient (the team), with concrete examples that map onto the category enum. It is distinguishable from the sibling feedback_list, which reads submissions rather than creating them, though it never names that sibling explicitly.

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 examples (bug, missing data, idea) imply when to reach for this tool, and "Read by people; not answered" sets the expectation that no reply will come back. However, it never says when NOT to use it — e.g., that feedback_list is the read-side counterpart — so routing guidance is only implied.

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