justhandled_community_rule_credibility_preflight

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

No annotations are provided, so the description carries the full burden. It discloses the $0.25 USDC cost and the general scope, but lacks necessary behavioral detail such as whether the tool performs a read-only check, what the return value is, whether it triggers a blockchain transaction, or if any external calls are made.

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 front-loaded purpose and cost. Every word earns its place; there is no redundancy or filler.

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?

This is a complex tool with a large nested schema and no output schema, but the description does not explain what the tool returns, how the payment is submitted, or what the caller should do with the result. Significant context is missing for the agent to invoke it correctly.

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 0%, and the description does not explain the meaning of the five parameters or any nested fields. It only loosely maps elements like 'Reddit, Hacker News, Show HN, Product Hunt' to the channel enum and 'community rules' to the community object, which is far too little to compensate for the complete absence of schema descriptions.

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 uses the verb 'Check' with a clear object: 'a proposed Reddit, Hacker News, Show HN, or Product Hunt action' and explicitly lists the criteria: official guidance, supplied community rules, account credibility evidence, and promotion boundaries. This is specific and distinct from sibling tools, which focus on different preflight topics (e.g., CSV schema, gitignore, redirect maps).

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 implies usage for checking a proposed action before it is taken, but does not explicitly state when to use it versus alternative tools. No exclusions or alternative tool names are mentioned, so the guidance is only implicit.

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