delimit_cost_optimize

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is read-only, whether it requires special permissions, or what side effects (if any) occur. The term 'Find' suggests scanning but lacks clarity on mutability or safety.

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 very concise, fitting in a single sentence with a bullet-like list of examples. It wastes no words, though it could be slightly more structured. For conciseness, it earns a 4.

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?

Despite having an output schema (not detailed here), the description omits any mention of return values or output format. It does not explain what the tool produces after analysis. Additionally, there is no differentiation from similar sibling tools, leaving context gaps.

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% (the parameter 'target' is fully described in the schema). The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 verb 'Find', the resource 'cost optimization opportunities', and provides specific examples (unused deps, oversized images, uncompressed assets), making the purpose highly specific and distinguishable from sibling tools like delimit_cost_analyze or delimit_cost_alert.

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 only includes '(Pro)' as a tier indicator but offers no explicit guidance on when to use this tool versus alternatives like delimit_cost_analyze or delimit_cost_controls. It does not provide when-not-to-use scenarios or prerequisites.

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