reflect

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

No annotations are present, so the description must disclose behavior. It does not reveal whether actions are read-only, mutating, cause side effects, require authentication, or have other implications. For instance, the 'execute' action could be destructive, but no safety information is given.

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?

While the description is brief (two short phrases), it is under-specified rather than concise. It provides no structured breakdown of actions, parameters, or usage examples, so the brevity is a liability, not a convenience.

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 high complexity (10 parameters, multiple actions, an output schema yet not shown), but the description provides virtually no context. It does not explain what 'outcome', 'verify', or 'execute' mean, how they relate, or what kind of output to expect, making the tool unusable for correct invocation.

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?

There are 10 parameters, and schema description coverage is 0%. The description does not explain the meaning or expected format of any parameter. Required 'action' is a bare string with no enum or examples, and optional fields like 'worked', 'memory_id', and 'project_path' are completely unexplained.

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 'Outcomes & verification operations' is an abstract category, not a specific verb+resource. It lists action names ('outcome', 'verify', 'execute') without defining what each does, and does not distinguish 'reflect' from sibling tools. The tool's purpose remains ambiguous.

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. The description does not mention any context, prerequisites, or exclusions, and fails to reference any sibling tools for comparison.

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