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

With no annotations supplied, the description carries the full burden and does disclose some real behavior: results are limited to the latest scan (no history), ordered newest first, and default-include open and accepted manual findings. It leaves material gaps, though: it never says how the status filter interacts with that default (does status=fixed override it?), says nothing about pagination despite a cursor param, and says nothing about permissions or volume limits.

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 sentence, front-loaded with the verb and resource, with no padding or marketing language. It is a long run-on that packs ordering, scope and defaults together, which costs a little parseability, but nothing is wasted.

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?

Seven optional parameters, no annotations and no output schema mean the description must define both the result set and, ideally, what a finding looks like. It defines the result set adequately (latest scan, newest first, open and accepted manual) but says nothing about returned fields or pagination behavior, leaving an agent unsure what it will receive.

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 57%, with origin and target_id well documented and the four enums largely self-describing, so the schema does most of the work. The description adds no parameter meaning at all beyond the word "filters" and does not clarify the status enum's default, which is exactly where the coverage gap sits. It neither compensates for the gap nor contradicts it.

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?

Specific verb and resource: "Lists the findings" scoped to "the latest scan of every skill, MCP server and repository", plus the manual-findings case and the "newest first" ordering. No sibling tool in this server lists findings, so it is distinguishable by default. The only drag is the tangled clause "and their open and accepted manual findings", which reads as both scope and default filter, making the resource boundary slightly fuzzy.

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?

Usage is only implied: the mention of "latest scan" plus "open and accepted manual findings" hints at the default result set, and "with filters" signals the optional narrowing parameters. There is no explicit when-to-use, no when-not, and no pointer to get_skill / list_skills for the underlying skill or server detail. An agent can guess reasonable use but is given no routing guidance.

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