delete_title

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

No annotations are provided, so the description carries the full burden. It mentions 'delete' indicating destructiveness, but does not elaborate on side effects, permissions required, or recovery options. The optional reset is noted but lacks detail.

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 sentence, which is concise but overly brief for a tool with 8 parameters. It lacks structure or front-loaded key information beyond the initial verb. There is no wasted text, but it could be expanded without losing 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's complexity (destructive action, 8 parameters, output schema exists), the description is severely incomplete. It does not explain what 'devkit titles' are, the effect of delete_all, the purpose of confirmation_token, or how output schema relates. The description fails to provide enough context for correct invocation.

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 coverage is 0%, so the description must compensate. It only mentions 'devkit titles' and 'reset Steam client state', failing to explain any of the 8 parameters (e.g., target, delete_all, confirmation_token). Parameter names provide hints, but the description adds no value.

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 (devkit titles), and mentions the optional reset of Steam client state. This distinguishes it from sibling tools like list_titles or upload_title. However, it could be more specific about the scope (e.g., delete from the system).

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 on when to use this tool versus alternatives, no prerequisites or when-not-to-use conditions. The description is too brief to help an agent decide between this and similar tools like upload_title.

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