Create an evidence-aware installation plan tailored to your framework (Next.js, Node.js, Shopify, or generic) to address attribution gaps and consent requirements.
Create a framework-specific, evidence-aware installation plan.
| Name | Required | Description | Default |
|---|---|---|---|
| framework | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Evidence-aware' hints at some internal logic but doesn't disclose what it does with evidence, whether it mutates state, or what side effects (if any) it has. No mention of read-only nature, output format, or dependencies.
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?
Single sentence, zero fluff, action verb front-loaded. Perfectly concise for the amount of content provided.
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?
For a planning tool with no output schema and no annotations, the description is too sparse. It doesn't describe the structure of the plan, what 'evidence-aware' means in practice, or how the output relates to sibling generate tools. An agent would not know what to do with the result or how to verify it.
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 0%, so the description must compensate for the single parameter. It mentions 'framework-specific' but doesn't explain how each enum value (nextjs, node, shopify, generic) affects the plan or what the plan will include. The parameter meaning is only implied, not clarified.
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?
States a specific verb (Create), a resource (installation plan), and qualifiers (framework-specific, evidence-aware). It implies a planning action distinct from the generate siblings, but doesn't explicitly name them or contrast with them.
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 the generate_* siblings. It doesn't say 'use this before generating an integration' or list any prerequisites or alternatives. The agent must infer usage from the tool name and context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.