topos_evaluate_code

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

Description reinforces annotations (read-only, never writes/runs) and adds detail about only reaching SIMPLE and SECURE, plus return value description. No contradictions.

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?

Description is a single, focused paragraph with front-loaded purpose. Every sentence adds value with no redundancy.

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?

Despite no output schema, the description enumerates return fields. All parameters are covered, and sibling differentiation is clear. The tool's scope and limitations are fully communicated.

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?

Schema coverage is 100% with descriptions for all parameters. The description adds context about generator availability (only SIMPLE and SECURE reachable), which aids understanding of preferences parameter.

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 the tool scores raw code on a quality lattice, specifies it is read-only, and distinguishes from siblings by noting that COMPOSABLE requires other tools.

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?

Explicitly states when to use ('for a snippet not yet on disk') and when not to use, with named alternatives (topos_evaluate_file, topos_evaluate_project).

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