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

Annotations already declare readOnlyHint=true and destructiveHint=false with openWorldHint=false, so the safety profile is covered and the description only needs to add discovery behavior. It does add that output is role-aware and covers workflows, but with zero parameters it never explains how the role is inferred — from caller identity, token, or defaults — which materially affects what the agent receives.

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 front-loaded sentence with the verb and the payload up front; no filler, no restatement of the title. Well sized for a zero-parameter discovery tool.

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?

With no output schema, the description is the only place the return value can be characterized, and 'guide to tools and investigation workflows' is only a rough sketch — structure, length, and whether it lists workflows by name are unknown. For a meta-tool whose entire value is the shape of the guide it returns, that is a meaningful gap.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% on an empty object, leaving no semantic gaps to fill.

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: 'Return a role-aware guide to available Zineps tools and investigation workflows.' That is clearly distinguishable from every sibling, which are concrete data operations rather than meta/discovery. The only ambiguity is what 'role-aware' means and how the role is determined.

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?

No explicit when-to-use: nothing tells the agent to call this first, or on failure, or when it is unsure which of the ~46 siblings applies. There are no exclusions and no alternatives ('call the concrete tool directly if you already know it' would have been valuable). Usage has to be inferred from the name alone.

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