bubble_export_schema

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds behavioral context by specifying the output format (TDD-format markdown) and the contents (entity summary table and field specifications), which goes beyond what annotations convey.

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, well-structured sentence that front-loads the action ('Exports the Bubble.io schema as TDD-format markdown') and then adds useful detail about the contents. Every word earns its place, with no filler or redundancy.

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 parameters and no output schema, the description carries the full burden of explaining the tool's behavior. It clearly states the output format and what the markdown includes, which is sufficient for the agent to understand the tool's purpose and expected result. No missing critical information.

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, and the schema coverage is 100% (empty schema). Since there are no parameter to document, the baseline for parameter semantics is 4, and the description does not need to add parameter details. It correctly focuses on the output.

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 the tool exports the Bubble.io schema as TDD-format markdown, and specifies the contents (entity summary table and detailed field specifications). This distinguishes it from sibling tools like bubble_get_schema or bubble_schema_summary, which likely provide schema data in other formats.

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 use when a TDD-format markdown export of the schema is needed, but it does not explicitly compare with alternatives or state when not to use it. Sibling tools like bubble_get_schema might be simpler alternatives, but no such guidance is provided.

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