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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. What the description adds beyond that is valuable: it enumerates the returned payload (connection state, allowed access, tool count, stores with product counts), which matters precisely because no output schema exists. It stops short of describing the not-connected case or what access values look like.

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?

A single sentence that front-loads the primary question (is the account connected) and then lists the secondary payload. Every clause maps to a distinct returned field, so little is wasted, though the trailing list is dense enough to read as a run-on.

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, no-output-schema status tool, enumerating the return fields is the main burden and the description discharges it. Minor incompleteness remains around the disconnected/error case and the meaning of 'access that was allowed', which an agent would want before branching on the result.

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 takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level detail is needed or missing.

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 (the owner's Komers account) and the exact facts returned: connection state, granted access scope, available tool count, and stores with product counts. That is far more specific than the title 'Komers connection'. It does not, however, distinguish this summary from siblings such as komers_store_status or komers_tools, which appear to expose overlapping data.

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 explicit when-to-use statement and no mention of alternatives. An agent must infer from the name that this is the entry-point status check before calling connect_komers, komers_tools, komers_store_status, or komers_call. Given four closely related Komers siblings, the missing routing guidance is a real gap.

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