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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: no input is required, the call is purely a catalog lookup, and results must be treated as the authoritative set of valid IDs. It stops short of describing ordering or size/caching behavior.

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-loaded with a one-line summary and clean headers, so an agent can skim it quickly. It is somewhat longer than necessary for a zero-parameter discovery tool, since the 'discovers reports for feed_report' point is repeated in the purpose, usage, and LLM guidelines sections.

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?

Everything needed to call it correctly is present: no inputs, the role relative to `feed_report`, and a description of the returned catalog fields. Although an output schema exists, the description still names the key return fields (report_id, title, description, input_schema), which helps the agent chain into `feed_report`.

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 the baseline is 4. The description correctly and explicitly states 'This tool does not require any input', matching the empty schema with no contradiction.

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 ('List available public ZEN SecDB feed reports') and immediately frames the tool as a discovery counterpart to `feed_report`. An agent can distinguish it from every sibling without opening the schema.

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?

Gives an explicit when-to-use list (discover report IDs, inspect filters, unsure which report matches) and names the alternative tool `feed_report` with the ordering rule 'use before feed_report whenever the correct report ID is not already known'. It also states the negative constraint not to invent report IDs or parameters.

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