bdesign_workflow_template_get

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds that the template is local and that the response includes exact revision and definition digest, but it does not explain failure behavior, permissions, or what "local" implies in this environment.

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 a single front-loaded sentence with no wasted words. It communicates the core read operation and the notable return details efficiently.

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 getter with one parameter and no output schema, the description sufficiently states what is read and that revision and digest are returned. The main remaining gap is the lack of templateId semantics and any error or permission context.

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?

There is a single required templateId parameter with 0% schema description coverage, so the description should clarify its meaning or format. It only indirectly implies that templateId identifies the local workflow template, without adding syntax, source, or lookup details beyond the parameter name.

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 uses a specific verb ("Read") and resource ("local workflow template definition"), and adds that it returns the exact revision and definition digest. It is clear what the tool does, though it does not explicitly distinguish itself from sibling operations like template_list, preview, or apply.

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?

The description implies usage for fetching an existing local workflow template by ID, but it does not state when to choose this over template_list, template_preview, or template_apply. The context is adequate but leaves alternatives implicit.

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