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

Annotations are empty, so the description carries the full behavioral burden. It does disclose one useful scoping fact — only 'published' dossiers are covered — but says nothing about ranking, permissions, rate limits, pagination beyond the schema's limit field, or what happens when no results match.

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 no filler, stating the action and scope immediately. It is efficient, though it is perhaps too compact given the tool's five parameters and lack of sibling differentiation.

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?

An output schema exists, so return values need no explanation, and all five parameters are fully documented in the schema. However, with no annotations and eleven sibling tools including overlapping list/read/search tools, the description is thin on the operational context an agent needs to choose and use it confidently.

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 description coverage is 100%, so every parameter (tag, limit, query, category, min_conviction) is already documented in the schema, including examples and defaults. The description only restates those facets and adds no new syntax, format, or constraint detail, so the baseline of 3 applies.

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?

The description gives a specific verb ('searches and filters') and resource ('published Tresslers Group intelligence dossiers') and enumerates the four filter dimensions an agent can use. It does not, however, distinguish this tool from close siblings like list_dossiers or search_intelligence_matrix, so the agent must still 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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The word 'search' and the listed facets imply it is the keyword/faceted lookup path, but with siblings such as list_dossiers and search_intelligence_matrix present, the description leaves the routing decision entirely to inference.

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