Build Blueprint Task Context

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

Description provides minimal behavioral insight. Terms like 'compact deterministic context slice' are vague. No annotations exist, so the description should disclose if the tool is read-only, has side effects, or requires specific authorization, but it does not.

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, efficient sentence. However, it is too concise and lacks structure; it could be expanded to improve clarity without becoming verbose.

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 6 parameters and no output schema or annotations, the description is incomplete. It should explain the return value's structure (e.g., what a context slice contains) and how parameters shape it, but it does not.

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 100%, so baseline is 3. The description adds no extra meaning beyond what the parameter descriptions already provide. It does not clarify how parameters like maxPrimaryFiles relate to the 'context slice'.

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?

Description clearly states the tool returns a context slice for a task from a Blueprint artifact. The verb 'Return' and resource 'compact deterministic context slice' are specific, but it doesn't differentiate from sibling tools like blueprint.compose or blueprint.scan.

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. The description does not mention prerequisites (e.g., must have a Blueprint from blueprint.compose) or situations where it should not be used.

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