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

Annotations only mark this as non-read-only and closed-world, so the description carries useful extra load: it discloses that a token is required, that the call returns the share link plus a ready message, and that participants must open the app once a day at testerexchange.com/earn. It stops short of saying whether an existing test would be replaced or what error conditions look like.

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 tight sentences, front-loaded with the key qualifier 'Free:' and closing with the '(needs a token)' prerequisite. Nothing is redundant, though the trailing parenthetical makes the prerequisite easy to skim past.

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, no-output-schema tool, the description covers the cost model, the token prerequisite, and what comes back (link plus ready message), which is the information an agent needs to call it correctly. The only gap is behavior on repeat invocation for the same package.

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 coverage is 100% and the single package_name parameter is already documented with an example format in the schema. The description adds only that the app must belong to the user ('one of the user's apps'), so the schema does the substantive work and baseline 3 applies.

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 opens with a specific verb and resource: 'open a test for one of the user's apps' so friends and family can join from the share link. That is clearly distinct from siblings like start_campaign or fill_from_exchange, though the description never names the alternative by name, which is why this falls short of a 5.

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 leading 'Free:' signals this is the no-cost path versus paid campaign tools, and 'so friends and family can join' implies the target audience. However, it never explicitly states when to choose this over start_campaign or fill_from_exchange, leaving the agent to infer the contrast.

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