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

No annotations are provided, so the description carries the full behavioral burden. 'Returns' implies a non-mutating read, and the enumerated return contents give real transparency about output, but the description says nothing about permissions, cost, behavior when no drawing is open, or whether the data is cached/live.

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?

A single front-loaded sentence that starts with the verb and the target resource, then lists the returned fields compactly. Every clause is substantive and there is no filler or repetition.

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?

With no output schema and no annotations, the description compensates by enumerating the returned statistics, which is exactly what an agent needs to know before calling. The remaining gap is minor: no note on failure modes (e.g. no active drawing) or on whether the reported statistics are scoped to model space vs. layouts.

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 takes zero parameters, which is the baseline-4 case; there is no signature to explain and nothing the description could add. The schema is empty, so no parameter-level detail is missing.

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 gives a specific verb ('Returns') and resource ('statistics of the current drawing') and then enumerates the exact content: entity count, breakdown by type, layers, bounding box extents, blocks, and layouts. This clearly separates it from the sibling tools, none of which are read-only inspectors, though it does not name any sibling explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the introspection tool to call when it needs an inventory of the open drawing. There is no explicit 'use this when...' clause, no statement of preconditions (e.g. a drawing must already be open), and no mention of alternatives, so the guidance is only implied.

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