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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, and the description reinforces that profile by confirming no media is read or uploaded. However it does not disclose what happens when the optional 'workflow' argument is omitted — whether it returns an index of all workflows or errors — which is the one behavioral question an agent actually has here.

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, zero waste, with the capability statement front-loaded and the negative scope immediately after. Nothing is repeated from the schema or annotations.

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 single-enum-parameter, read-only documentation tool with no output schema, the description adequately conveys the shape of the returned content. The only real omission is the optional-parameter behavior, which matters but is minor at this complexity level.

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% and the description never mentions the 'workflow' parameter at all, so it adds no meaning beyond the enum list. The enum values are self-descriptive, and the required array being empty raises the unanswered question of default behavior, which the description should have resolved.

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 ('Get') and enumerates the exact content returned: formats, file handling, limits, and steps for a named workflow. The scope disclaimer ('public guidance only; does not read, upload, or process media') sharply separates it from any media-processing operation. There are no siblings to distinguish from, which keeps it just short of a 5.

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 exclusion ('does not read, upload, or process media') implies this is a lookup/consultation tool rather than an action tool, but there is no explicit statement of when to call it (e.g. 'call before submitting a job'). With no siblings, no alternatives need naming, so the implied usage is adequate but thin.

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