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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results come from cutgpt.app, include what each tool does and whether it uses AI, and are free with no subscription. It still omits result-count/pagination behavior, but the added cost and return-content info is real value.

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?

Two sentences, front-loaded with the core purpose before the category enumeration and the return/cost notes. The category list is long but each item earns its place by exemplifying valid 'task' inputs, so it is efficient overall.

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?

An output schema exists, so return-value structure need not be explained, and annotations fully carry the safety profile. Remaining gaps are the undocumented 'limit' parameter and the absence of any routing guidance against the many sibling tools, which for a discover-style tool leaves the agent to infer when to choose it.

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 description coverage is 50%: 'task' is documented in the schema while 'limit' is not. The description reinforces the task concept by enumerating acceptable task categories ('resumes and cover letters', 'citations', 'flashcards', etc.), which helps scope the required param. It adds nothing for 'limit', so both the schema and description leave that parameter unexplained.

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 specific verb and resource ('Find a free, single-purpose web tool for a task') and enumerates the concrete task categories it covers. It also implicitly distinguishes itself from siblings like find_ai_guide (guides) and recommend_ai_assistant (assistants), since this returns tools on cutgpt.app.

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 makes the domain of applicability clear through its example task list, so usage is strongly implied. However, it never states when to prefer this over alternatives such as find_ai_guide, recommend_ai_assistant, or find_ai_guide, and gives no exclusions.

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