bubble_tdd_validate

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the reporting specifics but no additional behavioral context such as auth requirements, failure modes, or side effects. While not contradictory, it does not enrich transparency beyond the annotations.

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 states the action, resource, and output categories without waste. Every clause contributes to understanding, making it highly concise and well-structured.

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?

The tool has one parameter, robust annotations, and the description explicitly enumerates the validation categories returned. Although there is no output schema, the report types are listed, making the behavior sufficiently clear for a simple validation tool. It omits the exact report format or exit codes, but this is a minor gap 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 input schema fully documents the only parameter (tdd_path) with a description and 100% coverage. The tool description adds no further parameter semantics, but the high schema coverage justifies the baseline score of 3, as the structured data carries the parameter meaning.

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 uses the specific verb 'Validates' with a clear resource ('TDD markdown file against the live Bubble.io schema') and explicitly lists the report outputs ('missing types, missing fields, type mismatches, and extra fields'). This distinguishes it from sibling tools like bubble_get_schema or bubble_record_validator by focusing on validation against the live schema.

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 usage context (validating a TDD file) but provides no explicit guidance on when to choose this tool over siblings, no exclusions, and no alternative references. It is adequate for an agent to infer the primary use case but lacks direct when-to-use or when-not-to-use information.

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