Goals Archive Goal

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

Annotations show non-read-only and non-destructive, but the description only adds 'may create or update Monarch data', a generic statement that does not explain the specific state change (e.g., setting an 'archived' flag). No mention of reversibility 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 very short (two sentences), but the second sentence is vague and unhelpful. It could be restructured to prioritize the effect of archiving over the generic data creation/update statement.

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 four parameters, no output schema, and similar sibling tools, the description is incomplete. It lacks explanation of return values, the effect on the goal's state, and parameter details beyond what the schema provides.

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 description does not reference any parameters. Although schema description coverage is 50% (fields and output_mode have descriptions), the required goal_id lacks explanation. The description should clarify that goal_id identifies the goal to archive.

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 'Archive goal', a specific verb+resource, but does not clarify what archiving means (e.g., marking as inactive) versus deleting or restoring. The vague second sentence about creating/updating data adds confusion and fails to distinguish this tool from siblings like goals_delete_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 like goals_delete_goal or goals_restore_goal. Prerequisites (e.g., goal must exist, cannot already be archived) are omitted.

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