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

No annotations are provided, so the description carries the full burden. It discloses that the tool is 'Browser-based', but does not explain how the generation works, what inputs are required, or what the output format looks like. The sparse detail leaves significant behavioral unknowns.

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 a single, focused sentence that front-loads the primary action and context. It is concise with no wasted words, and the qualifier 'Browser-based tool' adds useful information without unnecessary length.

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 simple browser-based tool with no parameters and no output schema, the description adequately covers the purpose, domain, and platform-specific nature. However, it does not specify which platforms are supported or what user input is required, which would enhance completeness. Still, it is sufficiently complete for the tool's simplicity.

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 input schema is empty (0 parameters), so the baseline is 4. The description correctly avoids inventing parameter details and does not need to compensate for schema gaps. No additional parameter semantics are required.

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 uses a specific verb '生成' (generate) and clearly identifies the resource as 'SNS投稿文' (SNS post text), with context '動画告知/切り抜き紹介' (video announcements/clip introductions) and 'プラットフォーム別' (by platform). This makes the tool's purpose specific and distinguishable from generic text generators.

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 implies the use case (when you need SNS posts for video promotions) but does not explicitly state when to prefer this tool over alternatives like youtube-description-generator or other template tools. No exclusion criteria or alternative references are given, so guidance is implicit rather than explicit.

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