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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the trailing 'Read-only' adds nothing beyond structured data. The description discloses no behavior beyond that — nothing about what the contract contains, whether contract_version changes the returned shape, or how large the payload is.

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 clauses, front-loaded with the resource identity and no filler. It is efficiently sized, though its brevity edges toward under-specification rather than tightness.

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, the description must carry the return-value burden, yet it never explains what the contract object looks like or what contract_version selects. An agent gets safety hints from annotations but not enough to call this confidently when the optional parameter matters.

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 50%: board_id is described but contract_version has no description anywhere. The prose mentions neither parameter, so it does not compensate for the undocumented optional param or explain how defaulting contract_version behaves. The description adds no parameter meaning.

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 identifies the resource — the automation format / workflow contract that the builder edits against — which hints at what is returned and distinguishes it from siblings like mcp_workflow_assets or mcp_workflow_tags. But it is a noun phrase with no verb; it never says 'returns' or 'retrieves', so an agent must infer the action. Purpose 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?

There is no when-to-use guidance and no mention of alternatives. 'Read-only' describes a trait, not a usage condition, and the description never says when an agent should call this versus opening a board or reading another workflow_* tool. No exclusions or prerequisites are given.

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