delete_blueprint_function

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

With no annotations, the description carries full burden. It only says 'delete' but does not disclose side effects (e.g., irreversible, cascade deletes), permissions needed, or whether the blueprint must be saved. The lack of behavioral context limits an agent's understanding of consequences.

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 concise sentence that immediately conveys the action and target. Every word earns its place with no redundancy or fluff.

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 simple two-parameter delete tool with an output schema, the description is nearly complete. It could briefly mention that the tool permanently removes the function and may fail if dependencies exist, but overall it covers the essential purpose.

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% (no property descriptions). The description does not explain the parameters: what 'function_name' refers to (e.g., exact name vs. display name, case sensitivity) or ensure clarity for 'blueprint_name'. No additional meaning is added beyond the schema.

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 'Delete a function from a Blueprint' clearly states the specific verb 'Delete' and the distinct resource 'a function from a Blueprint'. It differentiates from sibling tools like 'delete_blueprint_node' (which deletes a node) and 'rename_blueprint_function' (rename, not delete).

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 is provided on when to use this tool vs alternatives (e.g., delete_blueprint_node, delete_blueprint_thing). There is no mention of prerequisites, such as requiring the function to exist or be unused, nor when not to use it.

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