Update Custom Format

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

No annotations are provided, so the description must convey behavioral traits. It only mentions the requirement for confirm=true, but does not disclose that this is a destructive update, what side effects occur, permission needs, or response 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 very short (two clauses), which can be concise, but it sacrifices essential information. For a tool with 15 parameters and no schema coverage, this level of conciseness is under-specification, not efficiency.

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 complexity (15 parameters, no output schema, no annotations), the description is extremely incomplete. It provides no return value, no comparison to siblings, no explanation of object structure for 'body,' and no context for when this update is appropriate. This is far from complete.

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 15 parameters with 0% description coverage. The description adds no meaning to parameters except that confirm must be true. It does not explain id, body, app, or any other parameters, leaving the agent with no guidance on how to fill them.

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 states 'Update a custom format by id,' which clearly identifies the action and resource. However, it does not differentiate from sibling tools like 'update_custom_format_score' or 'duplicate_custom_formats,' so it lacks explicit sibling 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?

Only one usage condition is provided: 'Requires confirm=true.' No guidance on when to use this tool versus alternatives, such as updating only the score or creating a new format. The description gives no context for appropriate invocation.

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