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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses real behavior: reports go to the Runtime team, the requester is notified when a fix ships, duplicates merge, and list returns status plus ship note with an hourly sorting cycle. It also states a data-safety boundary. This is rich context that annotations alone do not convey.

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?

It is dense but front-loads the value proposition ('Reports go straight to the Runtime team...') and then walks the two actions in order. Some clauses are run-on (the kind enumeration, the sorting note), but each sentence carries information.

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 10-parameter tool with no output schema and mutation semantics, the description covers both actions, the lifecycle of a report, and submission constraints. It stops short of stating what submit returns (the schema notes an idempotencyKey is returned), leaving a small gap in the round-trip picture.

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 70%, so much is already documented, but the description adds routing meaning by grouping the 'kind' categories under the submit action and clarifying that 'requestId' comes from the error being reported and 'competitor' names another provider. The action enum (submit vs list) is only made meaningful here, which is the required parameter.

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 states specific verbs and resources across two actions: 'submit(...)' for filing a bug/gap/idea and 'list(limit?)' for viewing this organization's reports. An agent can distinguish the two modes immediately, but no sibling tool (e.g. runtime_support, runtime_notices) is named to differentiate this feedback channel from adjacent support paths.

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 clear context for each action: submit when you hit a bug, limit, missing feature, doc gap, slowness or competitor gap (and praise), list to see org reports. It also states submission hygiene ('give what was tried, what happened and the requestId, never credentials, private files or user data'). What's missing is explicit routing against the sibling support/reporting tools.

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