Get Site ID by Domain

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and 'Look up' is consistent with those. The description adds the context that the result is a siteId for downstream setup, but it does not disclose details like multiple matches, return shape, or error behavior; partial-match behavior appears only in the schema.

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 short sentences, with the core lookup operation front-loaded and the use-case motivation in the second sentence. No filler or redundant detail.

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 one-parameter lookup with strong annotations and a fully described schema, the description is nearly complete. It conveys both the input (domain) and the purpose of the output (siteId), though it stops short of specifying the exact output representation because there is no output schema.

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 100%, so the input schema fully documents the single required parameter, including the partial-match example. The tool description adds no parameter meaning beyond what the schema already provides, which matches the baseline for full schema coverage.

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 clear action ('Look up a site ID') on a clear resource ('by domain name'), and the title reinforces this. It does not explicitly distinguish itself from siblings like rybbit_get_site_details or rybbit_list_sites, but the lookup-by-domain purpose is specific enough to avoid serious confusion.

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?

Explains the use case ('needed for tracking setup and analytics queries'), giving an agent a clear reason to select this tool. It does not name alternatives or state when not to use it, so it stops short of a full 5.

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