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

With no annotations at all, the description bears the full burden. It discloses one useful behavior — results are ordered by priority — but says nothing about pagination, result size, permissions, or whether disabled workflows are included, and there is no output schema to fill the gap.

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?

A single tight sentence with the resource front-loaded and the ordering note appended. No waste, though the parenthetical gloss could have been spent on routing or parameter meaning instead.

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 four-parameter list tool with no annotations, no output schema, and two undocumented parameters, the description is too thin. It leaves unanswered whether the list is paginated, whether disabled workflows appear, and how project_id vs project_slug interact.

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 only 50%: project_id and project_slug are documented, while 'enabled' and 'trigger_type' have no schema description. The description mentions only that results are scoped to a project and gives no meaning for the enabled flag or the seven trigger_type enum values, so it does not compensate for the coverage gap.

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?

Clear verb+resource ('List visitor workflows for a project') with an added gloss clarifying what a workflow is (trigger + branching graph automations). It implicitly separates workflows from plain automations, but never names list_automations or get_workflow as distinct siblings, so an agent must infer the boundary.

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 gives no when-to-use guidance: nothing about when to prefer this over list_automations or get_workflow, and no mention of prerequisites such as needing a project context. The only usable signal is the 'for a project' scoping phrase.

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