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

The description discloses that GYOTAK records the report and later verifies that the post is public and contains the referral URL. Since no annotations are provided, this gives adequate transparency about the tool's behavior and follow-up.

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 concise sentences, front-loading the core action and then providing essential use instructions. No redundant wording is present.

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?

The description covers what to do, when to do it, and what happens after reporting. It does not describe the response format or failure handling, but the absence of an output schema makes this acceptable.

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?

The schema already covers all parameters, and the description reinforces that post_url must be a public https URL and that customerKey can be omitted under certain conditions. This adds practical meaning beyond the bare field names.

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 clearly states the tool's purpose: reporting a social media post that promotes GYOTAK with a referral URL. It also distinguishes this action from related referral tools by emphasizing the post-reporting step.

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 explicitly says to call 'right after posting' and to include the platform and public URL, giving clear when-to-use guidance. It does not explicitly contrast with sibling tools like my_referrals or apply_referrer, but the timing and action are specific enough.

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