delete_smb_share

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

With no annotations, the description carries full burden. It reveals the safety mechanism (confirm=True) but does not disclose whether deletion is irreversible, if it sends notifications, or any side effects. This is minimal but not misleading for a simple delete tool.

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, front-loaded sentence of 9 words with zero waste. It places the core action first and adds a crucial condition concisely.

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 tool with 2 parameters and an output schema available, the description is nearly complete. It could mention if the action is irreversible or other prerequisites, but the given information is sufficient for basic use.

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 0%, so the description compensates by explaining the id parameter (identifies the share) and the confirm parameter (must be true). It does not repeat schema types but adds semantic meaning beyond the JSON 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 clearly states the action (Delete), the resource (SMB share), and the method (by ID). It also highlights the crucial confirm=True requirement. This distinguishes it from sibling tools like create_smb_share or list_smb_shares.

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 explicitly requires confirm=True, which is a key usage condition. However, it does not mention when to use this tool versus alternatives or provide exclusions. The context is clear enough for a delete operation, but it misses alternatives or when-not-to-use guidance.

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