Goals Update Goal Event

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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds the key behavioral trait that it 'may create or update Monarch data', which is beyond the annotations. However, it does not explain the conditions under which creation vs update occurs, nor does it disclose other behavioral aspects like required permissions or side effects.

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 with no redundancy. The first sentence states the core action, and the second adds a critical behavioral note. Every word earns its place, making it highly efficient.

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?

With 7 parameters, low schema coverage, no output schema, and minimal annotations, the description is far too sparse. It does not explain the tool's purpose relative to goal events, what each parameter does, or what the return value looks like. An agent would struggle to invoke this tool correctly without additional context.

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 only 29% (descriptions for fields and output_mode). The description provides no parameter-level guidance. It does not explain the meaning or usage of event_id, date, notes, include_in_budget, or session_path. Given the low coverage, the description should compensate but does not.

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 'Update goal event', identifying the verb and resource. However, the addition 'This may create or update Monarch data' introduces ambiguity—an update tool should not typically create data, and this mixing reduces clarity. It does not explicitly distinguish from siblings like goals_create_goal or goals_contribute_to_goal.

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 (e.g., goals_contribute_to_goal, goals_withdraw_from_goal). There is no mention of prerequisites, context, or exclusions. The agent must infer usage solely from the tool name and description.

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