update_event

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

With no annotations, the description carries the full burden of behavioral disclosure. It simply states 'Update a PocketSmith event' without explaining side effects, the meaning of the 'behaviour' parameter (one/forward/all), or any potential impacts on the event series. This is essentially a tautology that reveals no behavioral traits.

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 with no wasted words, but it is under-specified to the point of being nearly useless. It does not earn its place by adding value beyond the tool name, and it lacks essential information about the operation.

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?

The tool has complex semantics (event series updates with 'one', 'forward', 'all' scopes) and no output schema or annotations. The description provides none of the necessary context about these behaviors, making it inadequate for an agent to safely and correctly invoke the tool.

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 covers 100% of the parameters with descriptions, so the baseline is 3. The tool description adds no additional parameter meaning beyond what the schema already provides, but it doesn't need to since the schema is comprehensive.

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 identifies the action ('Update') and the resource ('a PocketSmith event'), which is specific enough to distinguish it from unrelated tools. However, it lacks any details about what can be updated or any contextual scope, so it doesn't fully differentiate from sibling create/delete event tools.

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 like create_event or delete_event. The description does not mention any prerequisites, series behavior, or context in which updating an event is appropriate.

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