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

Annotations declare readOnly and non-destructive, and the description reinforces this with 'Creates nothing,' while adding information annotations do not carry: no account is required, and the draft itself is produced later by the user pressing 'Make my draft' in the browser. It stops short of saying whether the link expires or is single-use.

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?

Front-loaded with the core action before the downstream behavior and the safety note. The parenthetical inventory of everything the sheet will contain is a bit long for a tool that does not build the sheet itself, but it does usefully set user expectations and no sentence is pure 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?

With no output schema, the description correctly explains the return value (a link) and what happens when it is opened. For a one-parameter, read-only tool this covers the essentials; only minor operational details (link validity, whether the words are URL-encoded) are left unstated.

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% for the single 'words' parameter, so the baseline is 3; the description goes slightly beyond by enumerating acceptable sources (email, notes, flyer text, event description), which helps the agent decide what text to pass. It doesn't add format or length guidance beyond that.

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?

States a concrete verb and output: 'Turn the user's ... words into a link that opens im-in.events' with those words pre-filled. The phrase 'Creates nothing and needs no account' implicitly separates it from create_signup_sheet, but the sibling is never named, so the differentiation is inferred rather than explicit.

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?

Gives clear context for use: whenever the user supplies an email, notes, flyer text or event description, this is the entry point. It also signals the tool is a precursor step ('Pressing Make my draft there builds the whole sign-up sheet'), but it never states when to prefer it over create_signup_sheet or list_templates.

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