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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description correctly confirms a pure inspection behavior (it only reports linkage and chat state) and adds that chat-enabled state is part of the read, but says nothing about permissions, latency, or what happens for a site with no Komers connection.

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?

One compact sentence with no filler, front-loading the linkage question and then the two follow-on facts. It is slightly awkward as a sentence fragment ('Whether this site is...') but nothing is wasted.

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 one-parameter read-only status tool with no output schema, stating the three pieces of information returned is close to complete. A brief note that an unlinked site yields a null/absent store would make it fully sufficient.

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?

With a single parameter at 100% schema description coverage ('Site slug (e.g. "kopitiam-muar") or id'), the schema fully documents the input. The description does not mention the site argument or its accepted slug/id forms, so it adds no meaning beyond the schema – baseline 3.

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 names the resource (this site's Komers link) and enumerates the three facts returned: linked?, which store, and AI chat enabled. That is specific and readable, but it never distinguishes itself from nearby siblings such as komers_status, komers_tools, set_site_komers_store, or connect_komers, which an agent could easily confuse with it.

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?

There is no when-to-use guidance at all: nothing says to call this before link_komers_store or set_site_komers_store, nor that it is the read-only counterpart to those mutation tools. The agent must infer the routing from the name alone.

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