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

With no annotations, the description carries full burden. It usefully discloses the data-source chain (journals for coords/owned modules, Spansh for outfitting stations, EDSM as fallback) and warns that 'prices/stock rotate; verify at the station'. However it omits any mention of auth requirements, rate limits, or what happens if journals are absent.

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?

Three compact sentences with the core purpose front-loaded, followed by mechanism and a caveat. Little waste, though the middle sentence is dense with tool names that could be tighter.

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, but for a 3-parameter tool with 0% schema coverage and no annotations, the description leaves parameters and the location/radius behavior unexplained. It is under-specified for its complexity.

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 3 parameters (journal_dir, max_stations, search_radius_ly), and the description never names or explains them. It hints at 'your current location' and 'journals' but adds no actionable semantics for overriding the directory, station count, or radius.

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 (build) and resource (cargo shopping list) and clarifies the output is an Anaconda max-cargo module list plus purchase locations near the player. It is distinguishable from siblings, though the 'Anaconda max-cargo' framing is jargon-heavy and assumes domain familiarity.

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 guidance and no routing away from sibling tools like spansh_find_nearby_stations or inara_search_nearest, which overlap with the 'where to buy' function. The agent must infer usage purely from the purpose statement.

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

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output is 'bounded' (not an endless stream), 'live' (real-time vs historical), and dependent on 'pyzmq + network', but it omits failure modes, rate limits, and what the bounding concretely means.

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?

The description is a single front-loaded sentence with no wasted words. The core purpose comes first, and the runtime dependency is placed parenthetically without disrupting the main clause.

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?

Output schema exists, so return values need not be explained. But with no annotations, 0% parameter description coverage, and no usage guidance, the definition leaves the agent unable to judge how to tune timeout_s or max_messages or when this live-sample tool is preferable to siblings.

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%, and the description does not mention timeout_s or max_messages. The word 'bounded' faintly relates to the limits but does not map to parameters or add semantic meaning beyond the schema titles and defaults, so it only partially compensates for the coverage gap.

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 specifies the resource (EDDN relay messages) and scope (bounded sample, live), so an agent knows it obtains a limited set of real-time EDDN messages. It does not explicitly differentiate from the sibling tools, which are mostly static game-data queries.

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 guidance on when to use this tool versus alternatives, nor any when-not conditions. The parenthetical 'needs pyzmq + network' is a runtime prerequisite, not usage guidance.

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

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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing beyond the '(EDSM)' data source: no rate limits, no indication of what happens when both a name and coordinates are supplied, and no note on result caps. A safe read-only call is implied but never stated.

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 compact sentence with zero filler and the core scope front-loaded. It is efficient, though the extreme terseness leaves it close to under-specified rather than optimally structured.

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 not be described, but with five optional parameters, 0% schema coverage, and no annotations, the definition omits essential calling context: how to pick a center, what the default radius means, and any limits on results.

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%, and the description partially compensates by naming radius_ly and indicating that either a system name or x/y/z coordinates can define the center. It does not explain the default radius of 15, units, or the mutual exclusivity/precedence of system_name vs coordinates, leaving real ambiguity.

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 resource (systems) and a specific scope (within radius_ly of a point), enough to distinguish it from edsm_system_info (one system) and spansh_find_nearby_stations (stations). It does not explicitly name a competing sibling, so it stops short of a 5.

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 statement of when to use this tool versus the many alternatives (edsm_system_info, spansh_query_systems, spansh_find_nearby_stations). Usage is only inferable from the phrase 'within radius_ly'.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only lists output fields and does not state that the operation is read-only, whether any authentication or rate limits apply, or how errors (e.g., unknown system) are handled.

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?

The description is short and front-loads the returned data, but it is a fragmented, slash-delimited phrase rather than a well-structured sentence. It avoids waste but is under-specified for the tool's scope.

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-value details need not be fully described. However, the description omits usage context relative to its many siblings and provides no parameter format guidance, leaving gaps for correct invocation.

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?

There is one required parameter (system_name) with 0% schema description coverage, and the description does not clarify its format, case sensitivity, or accepted values. It only implies 'one system', which is insufficient to compensate for the undocumented schema.

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 names a specific resource (one system) and enumerates the data returned (population, government, stations, claimable assessment), so the agent knows what it does. However, it does not differentiate this tool from EDSM sibling edsm_sphere_systems or the generic spansh_query_systems, leaving ambiguity about which to choose.

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 explicit when-to-use guidance, no mention of alternatives, and no exclusions. The phrase 'for one system' implies a single-system lookup but does not help the agent decide between this and the many other system/stations tools.

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

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

With no annotations, the description carries the full burden and discloses a multi-step pipeline (anchor resolution, EDSM sphere search, batch detail lookup, filtering, deduplication) plus the exact filter criteria (zero-pop, uncontrolled, stationless). It does not mention read-only safety, rate limits, or authentication, but the search nature implies a safe read operation.

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?

The description is short and front-loads the core purpose before the centre formats and workflow. The arrow-chain workflow is terse but each line contributes distinct information, with no obvious filler.

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?

Given no annotations, three parameters, and an output schema already present, the description is adequate but incomplete. It covers purpose, centre formats, and internal workflow, but omits semantics for two parameters and any behavioral notes on rate limits or result volume, leaving gaps an agent could need before invoking it.

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% and the description only explains one of three parameters: centre's accepted formats ('teapot', EDSM system name, 'x,y,z'). It says nothing about radius_ly units/meaning or max_candidates behavior, leaving two parameters undocumented beyond their names and defaults.

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 states a specific outcome: zero-pop, claimable systems near a centre, which distinguishes it from generic system or station search siblings. However, it does not explicitly name an alternative tool or contrast itself against edsm_sphere_systems or spansh_find_nearby_stations, so sibling differentiation is left implicit.

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?

The workflow bullet implies how the tool operates and the centre formats are given, so usage is inferable. But there is no explicit when-to-use guidance, no exclusions, and no reference to alternative sibling tools for nearby-system or station searches.

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

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

No annotations are provided, so the description carries the full burden, and 'from local journals' is the only behavioral clue (data source). It says nothing about read-only safety, auth/permission needs, staleness of local journal data, or what happens when journals are absent.

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 compact sentence-fragment with no filler, front-loading the returned fields. It is efficient, though its fragmentary style contributes to the missing verb/action.

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 needn't be explained, but the one input parameter is entirely undocumented and there is zero usage context. For an aggregate status tool with many overlapping siblings, this leaves notable gaps.

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% for the single 'journal_dir' parameter, and the description never mentions it, so the agent gets no help on what directory it expects, its format, or its default-null behavior. With one undocumented parameter this falls below the 3 baseline that a fully covered schema would earn.

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 enumerates the returned fields (commander name, system/station, ship, credits) but never states a verb or action, reading as a noun phrase rather than a description of an operation. It gives a partial sense of scope versus siblings like get_current_location or get_ship_loadout, but doesn't explicitly frame itself as an aggregate status snapshot.

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 mention of alternatives among the many location/ship/inara sibling tools, and no exclusions. The agent is left to infer that this is a broad status read versus the narrower siblings.

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

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

With no annotations provided, the description must carry the behavioral burden, and it does disclose the provenance (latest Location/FSDJump/Docked event), which tells the agent the result reflects the most recent relevant journal entry. However, it says nothing about read-only nature, failure modes when no event exists, or staleness 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?

A single compact sentence with no filler, front-loading the returned data and its source. It leans toward under-specification rather than verbosity, but every word carries information.

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 the terse description needn't enumerate return fields. Yet the undocumented journal_dir parameter and absent failure/empty-state behavior leave gaps for an agent calling the tool without prior knowledge.

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 single parameter journal_dir has 0% schema description coverage, and the description never mentions it. An agent cannot tell whether journal_dir is required, what format it takes, or what the default behavior is when omitted.

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 resource (current system, coordinates, station) and the data source it derives from, so an agent immediately knows this returns the player's present position. It is distinguishable from siblings like get_ship_loadout or get_commander_status, though the terse phrasing leaves the exact field set to the output 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?

The description names the underlying journal events but gives no guidance on when to call this versus alternatives such as get_journal_history or get_commander_status. No prerequisites (e.g., needing a journal_dir or prior game session) are mentioned.

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

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. It discloses ordering and example event types only; it omits read-only/security semantics, how 'relevant' is determined, pagination behavior, and what journal_dir or limit actually do.

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 resource and ordering, followed by illustrative examples. No unnecessary words are used.

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 annotations, 0% parameter coverage, and an output schema that only offloads return-format explanation, the description is too thin. It leaves the two parameters, selection logic, and usage context undocumented.

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% and the description mentions neither limit nor journal_dir. It adds no semantic information beyond the bare parameter names, so an agent gets no guidance on what journal_dir expects or what limit controls.

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 the resource (journal events), ordering (newest first), and examples of event types (FSDJump, Docked, Loadout). It does not differentiate from sibling tools like get_commander_status or get_ship_loadout, so clear but no sibling routing.

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 when-to-use guidance, no alternatives, and no conditions are provided. An agent must infer when journal history is preferable to the many sibling status, location, and search tools.

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

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

No annotations are provided, so the description carries the full load, and it does disclose the data source ('latest Loadout event'), which tells the agent the value is derived from journal data and may be stale. It says nothing about what happens if no Loadout event exists, whether results are cached, or permissions, leaving real gaps for an unannotated tool.

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 short sentence with no filler and the resource front-loaded. It is efficient, though the telegraphic fragment style leaves no room for the context an unannotated tool needs.

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 not be described, and the source is identified. However, for a tool with no annotations and an undocumented parameter, the definition omits error behavior (e.g., no Loadout event found) and the meaning of journal_dir.

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%, and the single optional parameter journal_dir is never mentioned in the description, so the agent gets no explanation of what it controls or what the null default implies. With one undocumented parameter, the description does not compensate for the coverage gap.

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 resource ('current ship + modules') and its source ('latest Loadout event'), which is enough for an agent to distinguish it from sibling tools like get_commander_status or get_current_location. It lacks an explicit verb and any named sibling it is not, so it falls short of a 5.

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 statement of when to call this versus alternatives, nor any prerequisites. The only implicit cue is 'latest Loadout event', which hints at recency but gives no guidance on conditions or exclusions.

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

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

No annotations are provided, so the description carries the burden. It discloses the external Inara API dependency and required API key, but does not state that it is a read-only search, mention rate limits, or describe error/side effects. The auth note is useful, but the safety profile is left implicit.

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?

One short sentence, front-loaded with the core action and data source; the auth prerequisite is parenthetical and compact. No filler.

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?

For a two-parameter tool with no annotations and 0% schema description coverage, the definition omits parameter roles, search value semantics, and alternative selection. The output schema covers returns, but callers still lack guidance needed to invoke it correctly.

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% for two parameters, so the description must explain them. It never mentions 'search' or 'system_name', and gives no format guidance or default behavior for 'search' (default 'station'). No parameter meaning is added beyond schema titles.

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 search action (nearest) and resource (stations/systems) and names the data source (Inara API). It is distinguishable from EDSM/Spansh siblings by the API, though it does not explicitly contrast when to prefer Inara over those alternatives.

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?

Only the prerequisite 'needs INARA_API_KEY' is given; there is no when-to-use or when-not-to-use guidance relative to sibling tools like spansh_find_nearby_stations or edsm_sphere_systems. The API requirement is helpful but does not select between competing tools.

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

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

No annotations are provided, so the description carries the full burden. 'Slimmed' is a useful hint that the payload is trimmed relative to a full station query, but there is nothing about result ordering, distance semantics, rate limits, or auth requirements for a Spansh-backed call.

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 compact sentence with the resource and scope front-loaded and no filler. It is arguably too terse, but every word does work and there is no redundancy.

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?

Output schema exists so return values need not be re-explained, but with no annotations, 0% parameter documentation, and four parameters, the description is too thin to make the tool safely callable without trial and error.

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% – x/y/z and max_results have only bare titles. The description's 'galactic coords' loosely maps to x/y/z, but max_results is never explained and no units, ranges, or defaults are given beyond the schema's default of 10.

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 the resource (stations), an implicit verb (find nearest), and the source (Spansh) along with a scope qualifier ('slimmed for shopping lists'). An agent can tell it returns station data, though it doesn't explicitly contrast with inara_search_nearest or spansh_query_systems, which is the main thing separating a 4 from a 5.

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?

The phrase 'for shopping lists' hints at a use case but there is no explicit when-to-use guidance, no mention of when NOT to use it, and no named alternative despite several overlapping siblings (inara_search_nearest, spansh_query_systems).

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only search but does not mention pagination, result limits, authentication needs, or any other operational behavior; the single filter example is parameter detail rather than behavioral context.

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?

The description is a single front-loaded sentence with no wasted words. However, its brevity borders on under-specification for a search tool whose parameters are otherwise undocumented.

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 not be explained. Still, with no annotations and no schema descriptions, the description is missing page behavior, filter semantics, usage guidance, and any indication of how the results are structured or limited.

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%, so the description must compensate. The example filter object adds meaningful syntax for the filters parameter, but the page parameter is not mentioned at all and the full filter schema remains undocumented.

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 states a clear verb+resource: a flexible search over Spansh systems. It does not differentiate this tool from sibling search tools such as edsm_sphere_systems or spansh_find_nearby_stations, so it falls short of a 5.

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 guidance on when to use this tool versus the many sibling search tools, nor any stated exclusions or prerequisites. The word 'Flexible' implies general applicability but offers no decision criteria.

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