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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description adds genuinely new behavioral constraints: the strict secret-handling rule (send '<set>' for BRIDGE_API_KEY or any *_KEY / *_SECRET, never the real value, since only presence and placement are checked) and the fact that it compares against the live app rather than static config. This is exactly the kind of context annotations cannot express.

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?

Front-loads the purpose in the first clause and keeps every sentence load-bearing, including the enumerated failure modes that justify the tool's breadth. The dense middle paragraph is long, but the detail is functional rather than padding.

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?

With no output schema, the description still specifies the return shape ('every concrete difference with its fix'), the input contract, and the remediation path via sibling tools. An agent has everything needed to call it correctly and act 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it scopes `env` to Bridge-related variables only and states the placeholder convention for secrets, and it explains that `framework` is inferred when omitted. The `app` parameter's 'omit to use current app' semantics live mostly in the schema, so this stops short of 5.

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 and resource ('Check a project's Bridge configuration against the real app') and then enumerates exactly what it detects (wrong app id, base URL pointing at another environment, unregistered callback URL, disallowed origin, missing variable, secret in browser-bundled var, signing-key availability). This makes it trivially distinguishable from siblings like get_environment_info or debug_auth_issue.

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?

Explicitly says what to pass ('only the Bridge-related variables from the project's .env files'), names the CLI equivalent (`bridge diagnose` reads .env itself), and routes follow-up work: get_environment_info for expected values, add_redirect_uri and update_app for fixes. When-to-use and alternatives are both covered.

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