Find Umami Website

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

The description adds fuzzy matching behavior beyond the readOnlyHint annotation. However, it does not mention the return format or if there are limits, but for a simple search it is sufficient.

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 concise sentence with a clear usage hint, no wasted words.

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?

Given the simple tool with one parameter, readOnly annotation, and no output schema, the description provides all essential information: purpose, usage context, and parameter meaning.

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% and the query parameter is already well described in the schema. The description adds minimal extra meaning beyond 'search by name or domain'.

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 clearly states the tool searches for Umami websites by name or domain using fuzzy matching, and the title confirms 'Find Umami Website'. It is distinct from siblings which are get/list operations.

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 explicitly says 'Useful before calling other analytics tools,' providing clear context for when to use this tool versus the other tools available.

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