Goals Restore Goal

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

The description adds 'may create or update Monarch data,' which is consistent with annotations but remains vague; it does not elaborate on side effects or authorization needs.

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 single-sentence description is concise but lacks sufficient detail; it is front-loaded but could be more informative without verbosity.

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 4 parameters and no output schema, the description fails to explain what 'restore goal' entails (e.g., undeleting vs. unarchiving) and offers no context on return behavior.

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 explain the parameters; schema coverage is 50% (only 'fields' and 'output_mode' have descriptions), yet the description adds no clarification for 'goal_id' or 'session_path'.

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 'Restore goal' with a specific verb and resource, distinguishing it from sibling tools like 'goals_archive_goal' and '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, nor any prerequisites or exclusions.

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