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

With no annotations, the description does real work: it declares the tool read-only, discloses that configId mode suppresses validation issues, and honestly frames the result as a snapshot of block configuration rather than an exact reconstruction. It does not cover permissions or error behavior, but for a read tool the key behavioral traits are surfaced.

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?

Front-loaded with the purpose in the first sentence, and both sentences carry information rather than filler. The second sentence is dense and grammatically tangled ("a snapshot of the blocks' configuration"), but no sentence is expendable.

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 and no annotations, the description steps up by describing the return content (field values, connections, validation issues) and the configId variant's behavior. It remains thin on the interaction between versionId and configId and gives no basis for choosing this over the closely named get_flow_instance_block sibling.

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 0%, so the description must carry all parameter meaning. It explains configId well (sourced from get_flow_instance and tied to that run's versionId) and implicitly nodeId, but workspaceId is never mentioned and versionId's role is only hinted at through the configId clause.

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 and resource ("full human-readable detail for one node") and enumerates what is returned: every current field value, its connections, and validation issues. It is clear without opening the schema, though it never names a sibling (e.g., get_flow_instance_block) to sharpen the distinction.

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?

Usage is only implied: the description explains where configId comes from (get_flow_instance) and that it fetches the block as it was at run start, which effectively signals a historical-inspection mode. There is no explicit statement of when to use this tool instead of get_flow_instance_block or get_block_schema, nor any when-not guidance.

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