osint_location_entity_search

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

No annotations are provided, so the description carries the full behavioral burden, yet it does not say whether this is read-only, what source it queries, or how results are scoped. The only behavioral hint is 'Negative Exclusion Filters', which maps loosely to exclude_terms.

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?

It is a single sentence with no wasted clauses, but the jargon 'Search Matrix' makes it less clear than a plain description would be. It is concise rather than under-specified, but still too thin for a 9-parameter 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 9 parameters, 0% schema description coverage, and no annotations, the one-line description is far too incomplete to guide invocation. The presence of an output schema relieves it of explaining return values, but input semantics and usage context remain largely absent.

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 0% across 9 parameters, so the description must compensate, but it only loosely gestures at location hierarchy and exclusion terms. It adds no meaning for entity_name, category_or_context, max_results, or how the location fields interact.

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 mostly restates the tool name with jargon ('Search Matrix') rather than specifying a concrete verb and resource. It implies location-based OSINT search with exclusion filters, but does not distinguish it from siblings such as osint_search or osint_geoint_lookup.

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 guidance, no exclusions, and no mention of alternatives among the many OSINT siblings. The phrase 'Hierarchical Location-based' hints that location fields matter but gives no selection criteria.

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