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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no repetition. The description adds real behavioral context beyond that: this is the authoritative source and must be consulted as a prerequisite to create_workflow. It does not say anything about output size or whether repeated calls are needed, which keeps it at 4.

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 sentences with no waste. The prerequisite ordering is front-loaded and the secondary routing information follows it, which matches the order in which an agent needs the facts.

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 no-input, no-output-schema reader the description covers what is returned (graph/settings schemas plus authoring instructions) and the sequencing constraint. It stops short of noting that the payload is likely large or that it should be read before validate_workflow/create_workflow specifically, which is the only gap.

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, so the baseline is 4; however there is nothing for the description to add or get wrong here, and the schema is trivially complete. A neutral 3 reflects that this dimension carries no discriminating information for a 0-param 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?

States a specific verb (read) and specific resources (authoritative graph/settings schemas, authoring instructions). It also explicitly says what this tool does not provide — scientific settings and exact ports — routing those to get_tool and get_workflow_tool, so the agent can distinguish it from siblings without opening any schema.

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?

Gives an explicit trigger condition ('before creating a workflow') and names the complementary tools (get_tool, get_workflow_tool) with the exact data each supplies. This is a rare case of both when-to-use and how-to-combine guidance in two sentences.

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