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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the domain meaning of a workflow, and the fallback rule that an empty search should be followed by listing all rather than reporting that nothing exists — a non-obvious behavior an agent would otherwise get wrong.

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?

Three short sentences, front-loaded with the action and scope, followed by the minimum domain definition needed and the entry condition. No filler, no repetition of the schema, and each sentence carries distinct information.

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 one-optional-param read tool with full schema coverage and no output schema, the description covers purpose, domain meaning and starting condition well. The remaining gap is what each list entry contains (id, name) that the agent would need to chain into describe_workflow or submit_request; without an output schema that would have been worth one clause.

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 100% and the schema entry for search_query already explains name-or-purpose matching and the empty-result fallback. The description itself adds no parameter meaning beyond that, so the baseline of 3 applies; it neither compensates for nor introduces anything the schema lacks.

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 with scope ("List the approval workflows this user can submit requests against") and even defines what a workflow is, so the agent knows the returned items carry fields and approvers. It does not explicitly distinguish itself from describe_workflow or list_workflow_templates, which are the nearest siblings, so differentiation is inferred 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?

"Start here when the user wants to submit something but has not named a specific workflow" gives a concrete entry condition and implicitly excludes the case where the user already named a workflow. It stops short of naming the alternative tool to call in that case (describe_workflow) or stating exclusions such as templates, but the usage context is clear without inference.

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