resolve

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

Describes side effects (storing in session.geometry_refs if label given) and output format, compensating for the lack of annotations. Does not cover all edge cases like error handling, but provides sufficient transparency for typical usage.

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?

Concise yet comprehensive: front-loaded with the primary action, followed by example, side effect, and output fields. Every sentence is essential and well-structured.

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's complexity (3 parameters, output schema exists but not shown), the description thoroughly covers inputs, outputs, and side effects. No apparent gaps for an agent to use it effectively.

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?

Adds meaning beyond the schema: explains selector as a Python expression with an example, object_name as a named object, and label's side effect. With 0% schema coverage, the description effectively compensates.

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?

Clearly states the verb 'Evaluate' and the resource 'selector expression against a named object'. Includes an example and output format, making the purpose unambiguous and distinct from sibling tools like 'measure' or 'clearance'.

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 usage through the description (evaluate selectors to get geometry descriptors) but does not explicitly state when to use or not use this tool over alternatives. No exclusions or alternative tool names provided.

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