design_ip

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

With no annotations, the description carries the full burden of disclosing behavior. It fails to mention whether the tool is destructive, requires authentication, or what side effects occur. It only states it 'designs' an intent, which is insufficient.

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?

Extremely concise, but at the cost of completeness. While no words are wasted, the description is too brief to be useful.

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 tool's name suggests design functionality and there is an output schema, the description should explain what an 'IP workflow intent' is and what the tool returns. It fails to provide any context, making the tool nearly unusable.

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?

The schema has 0% coverage and the only parameter 'params' is a generic object. The description adds no meaning beyond the schema, providing no information about what properties the object should contain.

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 'Design an IP workflow intent' is vague, lacking a specific verb and resource. It does not distinguish from sibling tools like 'design_block_design' or 'create_workflow', making it unclear what 'intent' means.

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 'design_block_design' or 'create_workflow'. The description implies a design action but offers no context or exclusions.

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