blueprint_generate_project

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

With no annotations, the description must disclose behavior. It fails to mention side effects (e.g., file creation, overwrite), safety, or requirements (e.g., workspacePath must exist). The overwrite parameter implies potential destruction, but this is not communicated.

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 sentence—concise but at the expense of completeness. It does not explain what a PBIP project is or how the blueprint is used, making it too brief for effective tool understanding.

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 the complex input schema with 4 parameters including nested objects, the description is severely lacking. No output schema is provided, and there is no information on what the tool returns or any usage context. It fails to cover essential aspects for correct invocation.

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 description coverage is 0%, and the description provides no explanation of the workspacePath or blueprint parameters. The blueprint object is complex with nested tables, columns, measures, relationships, and report pages, but the description offers no guidance on how to structure it.

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 action (Create) and resource (PBIP project) and indicates input type (high-level dashboard blueprint). It distinguishes from sibling tools like blueprint_apply and blueprint_validate. However, it doesn't mention the workspacePath parameter or the output, which limits full clarity.

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?

No guidance on when to use this tool versus alternatives such as blueprint_preview or blueprint_apply. The description does not specify prerequisites or the context of generating a project, leaving the agent without decision support.

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