Validate Blueprint

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

The description clearly states 'without creating or modifying any resources', but the annotations specify readOnlyHint: false, which contradicts this read-only behavior. This contradiction severely undermines transparency despite the other behavioral details provided.

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 somewhat long but every sentence carries useful information, from purpose to usage notes to API details. It is front-loaded with the core purpose and remains structured without waste.

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?

Given there is no output schema, the description adequately explains the return value ('returns a plan indicating the resources that would be created'), and also covers request format, size limit, API endpoint, and usage positioning relative to sibling tools, making it complete for the tool's complexity.

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 valuable clarification about passing the file contents as text rather than a path, reinforcing the file parameter semantics beyond what the schema states. The ownerId parameter is already well-documented.

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 states a specific action ('Validate a render.yaml Blueprint file') on a specific resource, and explicitly notes it does not create or modify resources. It also distinguishes itself from render_update_blueprint and render_retrieve_blueprint by describing the validation and plan-returning behavior.

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 explicitly instructs to validate before render_update_blueprint, provides clear usage instructions ('Pass the render.yaml contents as text in file — a path is not read for you'), and specifies the multipart/form-data content type and 10MB size limit, giving clear context for when and how to use the tool.

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