popper_solve

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

No annotations are provided, so the description alone must disclose behavior. It mentions being 'model-free conductor' and reporting phases, but omits side effects, state changes, prerequisites, or what the output actually contains. Minimal behavioral detail is insufficient for safe agent invocation.

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 a single, well-formed sentence that efficiently conveys the tool's purpose. Every word earns its place, with zero redundancy or irrelevant detail.

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 tool has 2 parameters, no output schema, and no annotations, the description is too sparse. It does not explain what 'phase' means, the role of 'statement', or the format of the report. An agent lacks sufficient context to use this tool correctly in a workflow.

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?

With 50% schema description coverage, only the 'depth' parameter has a schema description. The tool description adds no semantic clarity: it does not explain 'statement' or how parameters affect behavior. The description fails to compensate for the schema's gaps.

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 that the tool reports the current phase and suggests the next popper_* tool to call, positioning it as a model-free conductor. This distinct purpose differentiates it from sibling tools that perform specific actions like hypothesize or refute.

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?

The description implies the tool should be used for orchestration—deciding which tool to call next—but does not explicitly state when NOT to use it or provide alternatives among siblings. The conductor role is clear, but exclusion criteria are absent.

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