generate_autonomous_goals

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

No annotations provided; description explains analytical inputs but doesn't disclose side effects (e.g., whether goals are persisted) or concurrency implications. Moderate transparency.

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?

Two sentences, front-loaded with 'TRIGGER', no fluff. Every sentence adds value.

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?

Output schema exists; description covers purpose, trigger context, and analysis types. Complete for a zero-parameter 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?

No parameters (schema coverage 100%), so description adds context by naming inputs (missed detections, quality trends, prompt patterns). Baseline elevated for zero-param tool.

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?

Starts with 'TRIGGER: Call this to generate prioritized goals from learned patterns.' Clearly states verb (generate) and resource (prioritized goals), differentiating from siblings like set_goal (manual) or update_goal (modify).

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?

Implies proactive triggering via 'TRIGGER' and mentions analyses, but no explicit when-not-to-use or alternatives. Score 3 for implied usage without exclusions.

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