bubble_compare_environments

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

Annotations already declare readOnly=true, idempotent=true, and destructive=false, providing safety transparency. The description adds that the tool detects schema changes, which is useful context but not deep behavioral detail (e.g., whether it hits live APIs or what happens on network failure). With annotations covering the safety profile, this is an acceptable level of additional transparency.

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 a single, front-loaded sentence that immediately states the core function. Every clause adds value: what it compares, between which environments, and what kinds of differences it detects. There is no filler or repetition.

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 no-param, no-output-schema tool, the description is adequately complete. It explains the input (implicitly none), the action, and the kind of information that will be produced (detected changes). It could mention the return format or what happens if environments are unreachable, but these are not critical gaps given the tool's 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?

The tool has zero parameters, so the schema is trivially fully covered. Per the baseline for 0 params, this dimension gets a 4. The description adds meaning by explaining the comparison action, but there are no params to clarify anyway.

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 clearly states a specific verb ('Compares') and a specific resource ('schema between development and live Bubble environments'). It differentiates from siblings like bubble_get_schema and bubble_export_schema by emphasizing the comparison/detection of changes. The listed detected changes (new types, removed types, etc.) make the tool's purpose unmistakable.

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 implies when to use the tool (when you need to know differences between environments) but does not explicitly state scenarios or exclude alternatives. It doesn't mention when to prefer this over bubble_get_schema or bubble_schema_summary. The guidance is present through listing the detection focus, but there are no explicit 'use this when' conditions.

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