Scan Blueprint Project

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

As no annotations are provided, the description must disclose behavioral traits. It indicates the tool is read-only (analyzes code) and returns an artifact, but does not mention side effects, permissions, rate limits, or error conditions. The description is adequate but not comprehensive.

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 that is front-loaded with the purpose. It is concise and efficient, though it could be slightly more structured for clarity.

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 lack of annotations and output schema, the description provides minimal context. It does not explain the return value in detail, performance implications, error behavior, or how to use the artifact with siblings. This is insufficient for complete understanding.

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 schema documents all parameters. The description adds no additional meaning beyond the schema, achieving the baseline score.

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 that the tool builds a file inventory, analyzes parseable code, and returns an analysis artifact for grouping. This distinguishes it from sibling tools like blueprint.compose or blueprint.group, which focus on different operations.

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 does not explicitly specify when to use or not use this tool. While it implies scanning is a prerequisite for grouping, no alternatives or exclusions are mentioned, leaving the agent without clear contextual guidance.

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