Delete Custom Schema

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

Description warns 'This is irreversible', adding context beyond annotations that already indicate destructiveHint=true. No contradictions; description aligns with and slightly extends annotations.

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?

Two short, clear sentences. First sentence states action and parameter; second warns about irreversibility. No unnecessary words.

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 delete tool with one required parameter and no output schema, the description provides all necessary information: what it does, the parameter needed, and a critical warning about irreversibility.

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?

Only one parameter (id) with schema description 'DotNet class ID'. The description restates this but adds no further meaning. Schema coverage is 100%, so description adds minimal value beyond 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?

Clearly states the verb 'Deletes' and resource 'custom schema by its DotNet class ID'. Distinguishes from sibling tools like machship_create_custom_schema and machship_get_custom_schema.

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 explicit guidance on when to use vs alternatives or prerequisites. The description only explains what the tool does, not when it should be chosen over other delete tools.

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