drawing_export

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds genuinely new context by disclosing that the export is lossy ('Marks missing fields; does not advertise perfect restoration'). That lossiness warning is exactly the kind of characteristic an agent cannot get from the annotation flags. It does not mention where the file lands or how conflicts between repeated exports are handled, keeping it below a 5.

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?

Two short sentences with the purpose front-loaded and the caveat second; nothing is wasted. The trailing clause 'does not advertise perfect restoration' is slightly awkward phrasing where a direct 'restoration may be incomplete' would read cleaner.

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, a fully documented three-parameter schema, and read-only annotations, the description covers what an agent most needs: that this is a bulk, lossy export to a local file. Remaining gaps are modest — the destination/return shape of the JSON is not described, though the readOnlyHint=true combined with local file output could confuse an agent about side effects.

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 100%, so all three parameters are already documented in the schema, including the important note that target_id comes from browser_list_tabs and that expected_layout_id acts as a guard. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 opens with a specific verb+resource pair ('Export every available drawing point and property to local JSON') and clarifies the scope as a complete dump rather than a targeted read, which distinguishes it from drawing_get and drawing_list. It stops short of naming those siblings explicitly, so differentiation is implied rather than stated.

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 'every available' phrasing implies this is the bulk-export path versus the single-object drawing_get, and the local-JSON framing implies a persistence use case. However, there is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g., that target_id is needed to scope the export to a specific tab).

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