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

Annotations supply the safety profile (destructiveHint=false, idempotentHint=true, openWorldHint=false) but say nothing about the sign-in ticket check or the restricted-network rationale, both of which the description adds. The description also states the return shape and the required follow-up call. It does not explain the mismatch between the read-like framing and readOnlyHint=false.

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 English text is front-loaded with the trigger condition, but the Japanese sentence restates the same behavior rather than adding information, roughly doubling length. The core purpose ('returns the list of the kit's files') is buried after the situational framing.

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 carries the return burden and does so: it names the file list and setup instructions, and directs the agent to call get_kit_file per file. Missing are failure behavior (invalid or expired ticket) and any coverage of the lang parameter.

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%: ref is documented in the schema and reinforced by the description's mention of passing the address after /g/. The lang parameter has only an enum and is never mentioned in the description, so the agent gets no signal about what it controls or which language it selects.

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 states a concrete effect: it takes a pasted nicetohave.app link, checks the sign-in ticket, and returns the kit's file list plus setup instructions. It clearly distinguishes itself from get_kit_file by naming the follow-up call, but it never distinguishes itself from get_kit, list_kits or search_kits, which an agent must guess between.

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 an explicit triggering condition (user pasted a 'nice to have' line) plus an exclusionary condition (you cannot download from nicetohave.app directly, e.g. restricted-network cloud session). It even sequences the next tool call. It lacks guidance on when to prefer get_kit or the list/search siblings instead.

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