Growwer setup instructions

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety needs no restating. The description adds genuinely useful context — the bridge lacks an API key and all data reads are blocked until one is configured — but says nothing about what the tool returns (step list, link, or config instructions) or whether setup can be completed through any tool.

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 sentences, no waste, with the blocked-data condition front-loaded so the agent immediately knows the trigger for calling it.

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?

A trivial zero-param read tool with annotations and no output schema; the description covers purpose and the blocking condition. Only the nature of the returned instructions is unstated, which is a minor gap given the simplicity.

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?

Zero parameters with 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 specific verb+resource: 'Explain how to finish connecting this bridge to Growwer.' That distinguishes it from data-reading siblings like growwer_get_guide and growwer_get_me, though it does not explicitly name those alternatives.

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?

Usage is only implied: because 'no project, order, wallet or seller data can be read until one is configured,' an agent can infer this is the tool to call when other calls fail for lack of an API key. There is no explicit 'call this first' instruction or named alternative such as growwer_get_guide.

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