Entity Statistics

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

Annotations already mark readOnlyHint=true, so the read-only safety profile is covered. The description adds useful behavioral context beyond that: the tool returns total_entities, by_type, and by_layer with sorted ordering, which helps set expectations for the response shape.

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 short, front-loaded with the action, and clearly structured. The 'unique to AutoCAD MCP Pro' claim is extraneous and does not help an agent invoke the tool, but it does not obscure the operational content.

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 zero-parameter, read-only analysis tool with an output schema, the description is complete. It names the output fields, explains the grouping and sorting, and is adequately scoped to the active drawing.

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?

The tool has zero parameters, so the schema is fully covered by definition. The description usefully documents the return object fields, which is the only input-free semantics an agent needs.

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 concrete action and output: analyzing the drawing and returning entity counts grouped by type and layer, sorted by count. It is clear enough to distinguish from drawing creation or modification tools, though it does not explicitly differentiate from the closely related analysis_layer_stats sibling.

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 is provided on when to use this tool versus analysis_layer_stats, analysis_select_by_type, or drawing_info. The uniqueness claim is about market positioning, not about usage context or alternatives.

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