delete_subject

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions that deletion affects 'all its versions' and explains the 'permanent' parameter's effect, it doesn't cover critical aspects like: whether deletion is reversible, what permissions are required, confirmation prompts, error conditions, or what happens to dependent resources. For a destructive operation, this is insufficient.

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 efficiently structured with a clear purpose statement followed by parameter explanations. The 'Args:' section is well-organized, though the initial sentence could be more front-loaded with critical behavioral information given the destructive nature of the tool.

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 destructive tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks information about return values, error handling, side effects on related resources, permission requirements, and recovery mechanisms. The absence of output schema means the description should ideally explain what confirmation or status is returned.

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?

With 0% schema description coverage, the description adds significant value by explaining all four parameters. It clarifies that 'subject' is the name to delete, 'context' and 'registry' are optional schema/registry names, and 'permanent' controls hard vs soft deletion. However, it doesn't explain parameter interactions or format requirements (e.g., subject naming conventions).

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') and resource ('a subject and all its versions'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'delete_context' or 'bulk_schema_cleanup', but the resource specificity (subject vs context/schemas) provides some implicit distinction.

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 guidance on when to use this tool versus alternatives like 'delete_context' or 'bulk_schema_cleanup'. It mentions the 'permanent' parameter but doesn't explain when hard vs soft deletion is appropriate, nor does it mention prerequisites, dependencies, or recovery options.

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