upload_title

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

No annotations provided; the description only states actions without disclosing side effects (e.g., file overwriting, destructive operations), permissions, or behavioral traits. With 20 parameters, many affecting behavior, 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 a single efficient sentence (12 words). It is concise, but the lack of additional structure or detail makes it less usable. Still, it earns its place by stating the purpose.

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 tool with 20 parameters, 3 required, and no annotations, the description is extremely incomplete. It omits explanations of key parameters, output schema, and usage scenarios.

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 schema has 0% parameter description coverage, and the description adds no information about any of the 20 parameters (e.g., what 'delete_extraneous' or 'verify_checksums' do). The description fails to compensate for the lack of schema documentation.

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 verb (upload, update, register/update) and the resource (title folder, runtime settings, Steam shortcut). It distinguishes this tool from siblings like list_titles, delete_title, run_title.

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 (e.g., when to use upload_title vs run_title). No context about prerequisites or conditions.

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