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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the response contains each workflow's id, title, and when-to-use note, and it prescribes the follow-up call to xtiles_get_workflow. It does not mention any auth or rate-limit considerations, keeping it short of a 5.

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 critical instruction ('Call this FIRST') is front-loaded and the follow-up action is stated at the end. It is somewhat repetitive in restating the same routing idea twice ('If there is any chance a prepared workflow already covers the request, check here before improvising' after already saying 'Call this FIRST'), which costs a point but does not bury the payload.

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?

An output schema exists, so the description is not obliged to explain return values, yet it still summarizes them (id, title, when to use it) and closes the loop by naming xtiles_get_workflow as the next step. For a zero-parameter discovery tool with full annotation coverage, nothing an agent needs is missing.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing parameter-related the description could add, and it correctly spends no space on inputs.

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 states a specific verb and resource ('List the pre-built xTiles workflows') and immediately defines what a workflow is ('curated, step-by-step recipes'), with concrete examples (digests, weekly reviews, briefs, onboarding). It clearly separates this discovery tool from the sibling action tools like xtiles_create_tasks or xtiles_get_workflow.

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?

It gives an explicit imperative to call this FIRST before assembling multi-step processes by hand, enumerates the triggering intents (set up, automate, schedule, onboard, 'have xTiles do something for them'), and names the alternative path ('proceed normally with the other tools' / improvising with individual xtiles_* tools) when nothing matches. This is close to ideal routing guidance.

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