remove_canned_service_part

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the action 'Remove' which implies mutation, but does not disclose whether the removal is permanent, if it cascades to other items, or any side effects. This is a minimal disclosure for a destructive operation.

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?

A single, concise sentence that states the action clearly without unnecessary words. It is appropriately sized and front-loaded with the verb, making it easy to parse quickly.

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 removal tool with two well-documented parameters and no output schema, the description covers the core action. It doesn't mention return values or error conditions, but these are often implicit for removal operations. The tool's simplicity means this is largely complete.

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 descriptions for both parameters are explicit ('The part line item ID to remove' and 'The canned service ID'), covering 100% of parameters. The description adds no additional meaning beyond these, so it provides no extra value for parameter understanding. Baseline 3 is appropriate given high schema coverage.

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 uses a specific verb 'Remove' and clearly identifies the resource as 'a part line item from a canned service template'. This distinguishes it from sibling tools like remove_canned_service_fee or remove_canned_service_labor by explicitly naming the part line item, making the purpose unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives. The implied usage is clear from the tool name and description, but there is no mention of alternatives or exclusions. An agent must infer that this tool is for removing parts specifically, as opposed to fees, labor, or tires.

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