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

Discloses anonymity, no PII collection, 30-day expiry, per-IP rate limit (5/24h), and nature as signal collector. No annotations provided, so description carries full burden and does it well.

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 sentences, front-loaded with main action, no redundant information. Efficient and clear.

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?

Covers purpose, behavior, constraints, and intent. Could mention expected response or error handling, but not critical for a submission tool.

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 has 100% coverage with detailed parameter descriptions. Description adds no extra parameter-level meaning, so baseline 3 is appropriate.

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?

First sentence clearly states verb 'submit', resource 'wantlist entry', and purpose 'telling TensorFeed what data you wish was served'. Distinguishes from sibling read-only tools (all 'get_' or 'check_' etc.).

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?

Provides usage context: 'Aggregated patterns inform TF's pipeline priorities', 'Signal collector, not a contract', and rate limit. No explicit exclusion or alternative mention, but siblings are all read-only, so this is the only write tool.

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