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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds useful context about what is inspected ('resolved' workflow ports vs. the direct-job schema), but says nothing about permissions, failure modes, or return 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?

Two tight sentences with no filler; the primary purpose is front-loaded and the disambiguating clause follows. Slightly cryptic wording ('direct-job input schema') costs it the top mark.

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 simple read-only inspection tool whose safety profile is covered by annotations and which has no output schema, the description adequately conveys purpose. However, it leaves both the identifier format and the returned 'resolved ports' shape unexplained, which an agent would need to call it confidently.

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 coverage is 0% for the single 'tool' parameter, and the description only implies it is 'a scientific tool' without clarifying whether the value is a name, ID, path, or version. With the schema doing no work here, the description fails to compensate for the gap.

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 specific verb ('Inspect') and a precise resource ('a scientific tool with its resolved workflow input/output ports'), which is more informative than a bare 'get tool'. It distinguishes itself from the direct-job schema view, though it never names the sibling tool that provides that alternative, so the differentiation is implicit.

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 gives a clear situational trigger ('before connecting graph nodes') and clarifies when the direct-job input schema is not what you want. There are no explicit exclusions or named alternative tools (e.g., get_tool), keeping it short of a 5.

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