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

Annotations declare readOnlyHint=true, and the description does not contradict that. It adds useful behavioral context: the locale default behavior ('de has no prefix'), the content of publicLinks, and the constraint that Smithery needs a public www URL rather than GitHub. It omits auth/rate-limit details, but read-only status is already captured by annotations.

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 front-loaded with WHAT, NOT, RETURNS, and USE sections, and is reasonably compact. However, it relies on unexplained abbreviations and jargon ('×7', 'machines', 'card', 'com.ikeytz/website'), which hinders readability. Every sentence contributes, but not every phrase is self-explanatory.

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 tool has only one optional, fully documented parameter, a read-only annotation, and an output schema, the description is complete enough to select and call it correctly. It adds the key disambiguation from the protocol endpoint, explains the locale-prefix behavior, and summarizes returned fields. The unexplained jargon is a minor gap but does not block invocation.

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 schema already documents the sole 'locale' parameter with 100% coverage, including enums, defaults, and prefix behavior. The description adds only marginal context such as 'de has no prefix' and 'NOT Italian', which mostly reinforces the schema. This is the baseline 3 case where the schema carries the param semantic load.

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 states a specific resource and action: it returns the HTML hub at /mcp-hub, and explicitly distinguishes this from the protocol endpoint ('NOT the protocol endpoint. Protocol remains POST https://www.ikeytz.com/mcp'). It also differentiates from get_it by noting it returns the same machines plus publicLinks. The cryptic '×7' and 'machines' jargon slightly obscure the purpose, but the core resource and scope are clear.

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 gives explicit usage guidance: 'USE to cite discovery URLs.' It also states exclusions such as 'NOT the protocol endpoint' and 'Not com.ikeytz/website', and clarifies that Smithery requires a public URL on www, not GitHub. It does not systematically enumerate all sibling alternatives, but it provides enough routing context for correct selection.

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