mesh_stats

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states what is measured but does not mention side effects (the name and 'Measure' imply read-only, yet that is not explicit), does not describe error behavior, performance characteristics, or the exact return format. For a tool with zero annotation coverage, this is a noticeable gap.

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 two sentences, front-loaded with the core purpose and followed by a practical usage hint. Every word earns its place; there is no filler or 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?

For a simple 2-parameter tool with no output schema, the description covers the scope of measurements and the primary use case. However, it omits obvious but potentially relevant details such as expected file parameter format (STL binary or ASCII), whether the tool returns a single object or a list of metrics, and any caveats about large meshes. These gaps keep it from being fully self-sufficient.

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 description coverage is 50%: only 'listComponents' has a description, while the required 'path' parameter is undocumented in the schema. The tool description does not compensate by explaining what 'path' should refer to (e.g., a filesystem path to an STL file). Since the description adds no parameter guidance, agents relying on it may not know how to fill the required field.

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 states a specific verb ('Measure') and resource ('an STL') followed by the exact set of measurements: volume, surface area, bounding box, watertightness, and connected components. This clearly distinguishes the tool from all sibling tools, which relate to notebooks, graphs, and literals, not mesh geometry.

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 gives clear context: 'Use this to check what a notebook actually produced.' That tells an agent when to reach for this tool. It does not explicitly name alternatives or state when not to use it, but given the sibling set, the context is unambiguous enough to infer there are no competing mesh tools.

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