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

With no annotations, the description carries the full behavioral burden, but it only confirms that the tool returns full Markdown text. It does not mention access restrictions, rate limits, error behavior, or how pagination affects whether the full document is returned. This is adequate for a simple retrieval operation but leaves meaningful gaps.

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 wording. It efficiently conveys the resource, output format, jurisdiction, and accepted identifiers.

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?

The tool is simple, the input schema is fully documented, and an output schema exists, so the description does not need to explain return values. It is nearly complete, though it could clarify pagination behavior or prerequisites given the absence of annotations.

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 the schema already explains both the document identifier formats and the page parameter. The description reinforces that the identifier may be a URL or official identifier from search tools, but adds little beyond the 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 states a specific verb and resource: retrieve the full Markdown text of a legislation document or court judgment. It also scopes the tool to Germany (DE) and identifies the accepted lookup keys as URL or official identifier, which clearly separates it from the sibling search tools.

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 implies this is the retrieval step after using search tools, since it says the identifier can be one returned by search tools. However, it does not explicitly state when to use this tool versus searching, or what to do if the identifier is unknown.

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 supplied, so the description carries the full disclosure burden. "Return … hierarchy" makes the read-only nature implicit and the scope limitation (Germany/DE only, static structural reference rather than case data) is stated, which is useful. It does not state whether this data is static/cached, whether any permissions are needed, or that results are a fixed taxonomy rather than query-dependent.

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 that opens with the verb and resource before the detail. The long parenthetical synonym chains ("First Instance / Trial / Municipal / District Courts") are dense but earn their place by letting the agent map local court terminology onto tiers; the sentence is long but not padded.

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 with zero parameters the call surface is trivially complete. What remains useful and is covered: jurisdiction scope (DE only) and hierarchical contents including sub-portals. What is missing is a note on whether other jurisdictions are supported by a sibling or variant, which matters given the German-only restriction.

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 there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly resolves the one ambiguity a parameterless call creates — that the scope is fixed to Germany (DE) — which adds value beyond the empty 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?

Names a specific verb ("Return") and a precise resource ("complete step-by-step multi-tier judicial hierarchy for Germany (DE)"), and enumerates the three tiers plus sub-portals so the agent knows exactly what content comes back. It does not distinguish itself from the close sibling search_tiered_court_decisions, which also deals with court tiers, so the agent must 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?

Usage is only implied: the description makes clear this is a reference/discovery listing (a hierarchy map) rather than a search, which hints it is a precursor to search_tiered_court_decisions. There is no explicit "use this when…" statement, no statement that it takes no filters, and no routing advice among the five 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?

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about authentication, rate limits, ranking/relevance behavior, pagination, or result completeness beyond the source API name. The supported-court list is useful scope information but not behavioral disclosure; for a search tool with zero annotation coverage this is a notable gap.

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, opening with the verb and jurisdiction. The nested parenthetical court list makes it dense and slightly harder to scan, 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?

An output schema exists, so return values need not be explained, and the parameters are fully described in the schema. What remains missing for a multi-source legal search tool is any indication of when to prefer it over its near-identical siblings, leaving the definition minimally viable.

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 100%, so the schema already documents query, court, and limit including the limit bounds and court enumerations. The description merely repeats the court list already present in the court parameter, adding no new semantics such as query syntax or ECLI format guidance beyond what the schema states.

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 (search German court decisions and precedents), names the underlying data sources (Rechtsprechung im Internet, OpenLegalData API), and enumerates the covered courts. It does not distinguish itself from the close sibling search_tiered_court_decisions, so an agent must 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 explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as search_tiered_court_decisions or verify_citation. The only implied guidance is the jurisdiction restriction to Germany, which an agent could infer from the name alone.

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 supplied, so the description carries the full burden. It usefully discloses the underlying sources (gesetze-im-internet.de, Rechtsinformationen des Bundes, European/International registries), which signals coverage and reliability characteristics, but it does not state read-only nature, result ranking, pagination behavior, or any rate/latency constraints.

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 that identifies the verb, geography, document classes, and sources with no filler. It is dense with named registries that partly duplicate the schema's query description, but nothing is truly 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?

For a three-parameter search tool with an output schema present and no annotations, the description covers what is searchable and where results come from, which is the essential context. The main gap is the mild tension between "Germany (DE) national legislation" and the mention of European/International registries without clarifying when each source applies.

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 query, year, and limit are all documented in the schema itself (keywords or statute title/number, optional enactment year filter, max results). The description adds nothing beyond that baseline, which is acceptable given the schema does the work.

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 pairs a clear verb ("Search") with a well-scoped resource ("Germany (DE) national legislation"), and enumerates the document types (statutes, acts, codes, regulations) plus the sources queried. It implicitly separates itself from search_case_law by focusing on legislation rather than court decisions, though it never names the sibling explicitly.

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: an agent can infer this is the tool for statutes and regulations rather than case law, and that it covers DE plus European/international registries. There is no explicit when-to-use/when-not-to-use statement and no pointer to search_case_law or verify_citation as alternatives for adjacent needs.

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 supplied, so the description carries the full behavioral burden. It discloses the tier taxonomy and the relationship to the court hierarchy tool, and 'search' clearly implies a read-only operation. It says nothing about result ordering, coverage of the corpus, or whether the tier filter is strict, which is thin for a tool with zero annotation coverage.

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 action and resource, then the tier taxonomy, then the pointer to list_court_hierarchy. It is dense but every clause carries information, with only the parenthetical court-type list ('Cantonal/Regional/County/Circuit') adding noise.

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, and all four parameters are documented. What is missing for a multi-jurisdiction search tool is resolution of the Germany-versus-Balkan conflict, the 'all' tier behavior, and precedence between tier and sub_court, which an agent needs to call 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 100%, so the baseline is 3. The description does add some meaning beyond the schema by mapping 'Tier 1/2/3' labels onto the enum values and by explaining that sub_court keys come from list_court_hierarchy. However, it omits the schema's 'all' tier value and does not clarify how tier and sub_court interact when both are supplied.

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 ("Search court decisions in Germany (DE)") plus a scoping dimension (judicial tier), which distinguishes it from a generic case-law search. It also names a sibling, list_court_hierarchy, as the source of sub-portal keys. Clarity is docked slightly because the geography is internally inconsistent: it claims Germany (DE) while the schema's examples ('kanton_sarajevo', 'okruzni_banja_luka') are Bosnian, leaving the agent unsure of the actual jurisdiction.

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 implied by the description of what can be filtered (tier, or a sub-portal key drawn from list_court_hierarchy), which gives a usable workflow hint. There is no explicit statement of when to choose this over the sibling search_case_law or search_legislation, nor any when-not guidance, so the agent must infer the routing.

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 at all, the description carries the full behavioral burden, and it does disclose something valuable beyond the schema: verification is performed against live external registries, which implies network latency and possible registry unavailability. It does not say whether an unverifiable or malformed citation raises an error or returns a negative result, nor anything about rate limits or authority of the check.

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 front-loaded sentence that leads with the verifier framing and then states scope and targets. Minor waste in the redundant 'No-Hallucination' label and the repeated example, but nothing that obscures the purpose.

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 one-parameter tool with an output schema (so return values need not be described), the definition covers jurisdiction scope and verification targets adequately. The remaining gap is failure-mode behavior — what a non-verified citation looks like — which is partly absorbed by the output schema.

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 the single 'citation' parameter is already fully documented, and the description only repeats the same example formats ('ECLI:DE:BGH:...' or 'BGB § 433') that the schema already shows. This is the expected baseline when the schema does the heavy lifting, with no additional parsing or normalization guidance added.

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 uses a specific verb ('validates') on a specific resource ('legal citations ... against official Germany and ECLI/ELI registries'), and the name plus wording make clear this is a verification tool rather than one of the sibling search_* tools. The 'No-Hallucination Citation Verifier for Germany (DE)' preamble is marketing framing, but the operational sentence behind it is precise.

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 scope ('Germany (DE)', 'format and live existence') implies you come here with a citation already in hand, whereas the siblings discover documents. However, it never states the when-to-use boundary explicitly — no 'use search_case_law to find a citation, use this to confirm one' routing, and no statement of what to do when verification fails.

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