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

With no annotations, the description carries the full burden. It usefully discloses cost (1 credit per call), wildcard matching semantics, and template syntax, but omits critical behavioral details: permissions required, whether remove is destructive or permanent, and what happens when an add conflicts with an existing route.

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?

Front-loads the purpose with 'Decide what flows where' and then packs useful mechanics, an example template, action list, and cost into minimal sentences. Every sentence adds distinct value with no filler or repetition.

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 an 8-parameter, multi-action tool with no annotations and no output schema, the description is helpful but incomplete. It does not say which parameters apply to which action (e.g., route_id for remove), nor does it describe what list returns. An agent would still need to infer operational details.

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 13%, so the description must compensate, and it largely does: it explains the semantics of from, to, when, contains, template, and action. Only route_id is left unexplained, and workspace is covered by the schema. This is strong but not complete.

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 domain action: it manages event-routing rules that forward events from one app to another. It clearly distinguishes routing from sending by describing the forwarding conditions, wildcards, and templates. It does not name sibling tools, but the core purpose is unambiguous.

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?

Offers the vague hook 'Decide what flows where' but gives no explicit when-to-use criteria or alternatives. It lists actions add, list, remove but does not explain when to choose each or how they relate to sibling hub tools like hub_send. Usage context is implied at best.

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