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

The annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it says the read reports which axis it used, reports the girders' extent and supports found, can return a plan drawing, and on the website runs as a background job to poll with job_status. It does not describe failure modes or authorization needs, but the added async and reporting behavior is substantive.

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 front-loaded with the core read action and is mostly made of relevant clauses about what is read and how to invoke it. It is dense and somewhat run-on in the first sentence, but the length is justified by the complexity of the bridge-reading operation.

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?

Given the complex read operation, optional parameters, read-only annotations, and no output schema, the description is largely complete: it explains what model elements are read, that a plan drawing can be returned, that the read reports its chosen axis and found supports, and that it should precede bridge_reshape. It stops short of documenting the exact return structure or failure behavior, which keeps it from a 5.

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 the input schema already documents axis, picture, supports, and deckGroups in detail. The description adds little parameter-specific meaning beyond mentioning the plan drawing and that the read reports the supports it found; baseline 3 is appropriate when the schema carries parameter semantics.

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 and resource: it reads the open bridge model as the Bridge Reshaper plugin does. It then enumerates exactly what is read, including deck, spans, supports, skews, girder/edge lines, bearings, substructure, direction, levels, and plan drawing, which clearly distinguishes it from siblings such as bridge_reshape.

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?

It explicitly says 'Use it before bridge_reshape' and notes that on the website it runs as a background job requiring job_status polling. It gives clear context for when to use the tool, though it does not name when-not-to-use cases or alternative read tools.

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