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

With no annotations provided, the description carries the full transparency burden. It discloses what is returned, the source of the code, the 2% commission with sticky-after-first-convert behavior, and the FREE/rate-limited pricing. It does not mention side effects like whether registration is persistent or what happens if already registered, but it provides meaningful behavioral context.

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 dense and front-loaded with the main purpose. Every sentence adds value (returns, usage incentive, alternative tool, pricing). The embedded pricing JSON is functional but slightly verbose; still, the overall structure is efficient.

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 single-parameter registration tool with no output schema, the description is quite complete: it explains what you get, how to use it, the earning model, stickiness, and pricing. It doesn't cover error scenarios or idempotency, but given the simplicity and the sibling pointer, it is adequately complete.

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 single parameter agentId is documented in the schema with 'Your agent identifier', giving 100% schema coverage. The description itself does not elaborate on the parameter, so it adds no value beyond the schema. 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?

The description clearly states the action: 'Register for the Flipr referral program.' It specifies the exact outputs (fliprBetRefCode and share URL) and differentiates itself from the sibling tool flipr_referral_link by calling it a helper for post-registration use.

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 clear context: use this to register and get your referral code, then share it to earn commission. It explicitly points to flipr_referral_link as an alternative for retrieving the share URL. It does not explicitly state when NOT to use this tool, so it misses full exclusion guidance.

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