get_mesh_stats

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Return...' without clarifying whether the tool is read-only, has side effects, requires permissions, or any other behavioral context. For a stats-gathering tool, this is insufficient.

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 very brief (two sentences plus a parameter list) and front-loaded with the main purpose. Every sentence is functional, but the structure could be improved by grouping related information (e.g., a separate usage note).

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 one parameter, no output schema, and no annotations. The description leaves 'detailed topology statistics' vague; the agent cannot infer the return format (e.g., counts, dictionaries) or understand edge cases. Given the lack of output schema, more context is needed.

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 0%, so the description must compensate. It notes that 'name' is a 'Mesh object name,' adding a type constraint beyond the schema's 'Name' title. However, this is minimal; the description does not explain the expected format or hint at validation rules.

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 returns 'detailed topology statistics for a mesh object,' using a specific verb-resource pair. This differentiates it from sibling tools that return specific mesh components (e.g., get_vertex_positions, get_faces, get_edges).

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 on when to use this tool versus alternatives. For example, it does not explain that for individual component queries one should use other sibling tools, nor does it mention prerequisites or typical use cases.

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