Drawing Bounding Box

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

The description ('Get') aligns with the readOnlyHint annotation, but it does not disclose additional behavioral traits such as the format of the bounding box (e.g., coordinate order or units). The annotation already covers the safety profile, so the description adds minimal extra context beyond confirming the read operation.

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, complete sentence that conveys the tool's purpose without unnecessary words. It is front-loaded and efficient.

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 description is sufficient for a simple query tool with no parameters and an expected output schema. It explains what the tool does, though it could mention the output format or coordinate system context. However, completeness is high given the tool's simplicity.

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?

There are no parameters, and the schema coverage is 100%. The description does not need to add parameter semantics. The baseline of 4 is appropriate for a parameterless tool.

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 action ('Get') and the resource ('bounding box of all entities in the drawing'). It is specific and distinguishes this tool from siblings like layout_list or analysis_measure_distance, which serve different purposes.

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 implies that this tool is for retrieving the overall extents of a drawing, but it does not explicitly state when to use it versus alternatives like analysis_measure_area or analysis_entity_stats. No exclusions or prerequisites are mentioned, leaving usage decisions to the agent.

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