tokportal_update_bundle

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

Annotations provide no behavioral hints (all false). The description adds only that it updates 'mutable bundle metadata' and lists fields, but does not disclose whether the update is partial or full replacement, what happens to omitted fields, error conditions, authorization requirements, or response behavior. The description adds minimal value beyond the schema.

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 two sentences (14 words), front-loaded with the action, and contains no fluff. Every word earns its place.

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 update tool with 3 params, no output schema, and neutral annotations, the description is minimally adequate. However, it omits the partial-update behavior implied by minProperties:1, does not mention idempotency_key usage, and provides no return value information. The gaps are moderate but not critical.

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 description coverage is 100%, so the schema already describes all parameters. The description reiterates the mutable fields (title, external_ref, auto_finalize_videos) which are already in the body property schema. This adds no new semantic meaning, but reinforces the purpose. Baseline 3 is appropriate.

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 'Update' and the resource 'bundle settings', and lists specific mutable fields (title, external_ref, auto_finalize_videos). This distinguishes it from sibling tools like tokportal_get_bundle (read) or tokportal_create_bundle (create).

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 vs alternatives (e.g., tokportal_create_bundle for new bundles, tokportal_publish_bundle for publishing). There is no mention of prerequisites, idempotency key usage, or when not to use this tool. This is a significant gap.

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