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

Despite all annotations being false, the description discloses key side effects: 'Writes feedback telemetry only; no payment, trading or other action,' 'Never submitted automatically,' and 'free text is classified then discarded.' This goes beyond the annotations by explaining the data handling and side-effect scope, which is valuable for an agent.

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 two sentences with no redundant words, front-loading the purpose and critical constraints. It is appropriately concise, though it could be arranged with bullet points for even quicker scanning, which is why it does not receive a 5.

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 complex tool with 17 parameters and no output schema, the description is too sparse. It does not explain how to choose the various feedback types, what the token represents, or what schemas are 'bounded.' This leaves significant gaps that an agent must fill via the schema alone, which many parameters lack descriptions for.

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 description coverage is only 18%, so the description must carry the burden of explaining parameters, but it only mentions the 'packet feedback token' and 'free text' (likely short_request_text). It does not explain the meaning or selection of the many enum-driven parameters like feedback_type, usage_reason, or desired_capabilities, leaving agents to rely solely on the enum names without additional context.

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 explicitly states the tool 'submits what you would have done next without enough Fishnet evidence,' clearly indicating its purpose as a feedback mechanism. It distinguishes itself from sibling snapshot tools by emphasizing it 'writes feedback telemetry only' and involves no payment/trading, making it unambiguous what the tool does.

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 provides a clear trigger condition: use when there is 'without enough Fishnet evidence.' It also states it is 'optional' and 'never submitted automatically,' and warns against including personal data. However, it does not explicitly contrast with the snapshot tools, so an agent must infer when to prefer this over its siblings, slightly reducing the clarity of when-not-to-use.

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