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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool provides links to sitemap, docs, contact, and discovery documents, which is a mild behavioral detail not covered by annotations. However, it does not disclose additional behaviors like response format or whether the content is static, and it relies on annotations for the safety profile.

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 entire description is a single sentence that front-loads the core purpose ('What Black Label Real Estate is') and then lists the included link types. Every word contributes value, with no redundancy or filler.

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 zero-parameter, read-only informational tool, the description adequately covers the tool's purpose and content. It does not specify the exact output format (e.g., text vs. HTML) or detail the structure of the links, but given the simplicity of the tool and the absence of an output schema, this is sufficient. A slightly richer description could mention the type of information returned, but it is not a critical gap.

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 tool has zero parameters, so the input schema provides no semantics to clarify. The description correctly mentions nothing about parameters, and the baseline for zero-parameter tools is 4. There is nothing missing here.

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's purpose: it provides an overview of what Black Label Real Estate (blbestate.com) is, along with links to its sitemap, docs, contact, and discovery documents. This is a specific verb+resource that distinguishes it from sibling tools like estate_search and estate_owner, which focus on real estate data rather than site information.

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?

While the description implies the tool is for general site information (contrasting with sibling estate tools), it does not explicitly state when to use this tool versus alternatives or provide exclusions. The usage context is inferred from the tool's name and description rather than spelled out.

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