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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's main added value is the workflow disclosure: the recipient, not the caller, completes the form on wisheroo.com. 'Nothing is created or charged' adds a financial/creation guarantee that annotations do not cover. It omits details such as whether the link expires or persists.

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 short sentences, front-loaded with the action and its output, followed by the handoff and the safety reassurance. No sentence is filler; even the closing no-charge clause serves the caller's decision to trust the tool.

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 two-parameter tool with no output schema, the description covers purpose, output shape (a link), and the human workflow. The main gap is behavior with omitted optional parameters, since both fields are non-required and no defaults are stated.

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 50%, with recipient_name documented in the schema and occasion left to a self-explanatory enum. The description compensates by explaining the effect of both parameters: the form arrives 'already filled' with name and occasion, which is meaning beyond the schema's bare enum list. It does not say what happens when a parameter is omitted, despite zero required parameters.

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: 'Build a link that opens the Wisheroo song form already filled with the recipient's name and occasion.' An agent immediately knows the output is a prefilled form link, though it never names the sibling start_wish_list_link to disambiguate the two link-building tools.

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 gives clear operational context ('Give the link to the person; they add the memories and finish on wisheroo.com'), which explains this tool's role as a handoff step rather than a completion step. It stops short of explicit when-not guidance or naming start_wish_list_link as the alternative for a different link type.

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