delete-logged-model

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

Without annotations, the description must carry the burden of behavioral disclosure. It only says 'soft-delete', implying reversibility, but does not explain what that means in practice (e.g., whether the model can be restored, or if there are cascading effects on related data). This is insufficient for a write 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?

The description is very short (one phrase), which makes it concise. However, it lacks structure and essential details, crossing the line into under-specification rather than effective conciseness.

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?

Given the tool has a single parameter, no output schema, and no annotations, the description should at least explain what a soft-delete means and any restrictions. It does not, leaving the agent with minimal context to decide or invoke correctly.

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 input schema has 0% coverage, meaning the parameter 'modelId' has no description. The description adds no meaning beyond 'by ID', which is already obvious from the parameter name. It fails to explain what 'modelId' refers to (e.g., a UUID or string identifier) or any constraints.

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 ('Soft-delete') and the resource ('LoggedModel'), providing a specific verb and resource. It distinguishes from other delete tools by specifying soft-delete, but could be more explicit about what 'soft-delete' entails.

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 versus alternatives such as delete-model-version or delete-run. There is no mention of prerequisites, side effects, or conditions under which this tool should be chosen.

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