fedlex_get_law_by_sr

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds extra behavioral context: it mentions that for repealed decrees, the successor law is provided if available. No contradiction with annotations.

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?

Description is well-structured with HTML-like tags but remains concise. Front-loaded with purpose and use case. Every sentence adds value, though could be slightly more streamlined.

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 a simple tool with one required parameter and an output schema, description covers what the tool does, when to use it, important usage notes, and expected output fields. Sufficient for correct selection and 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?

Schema has a description for sr_number parameter with examples. Description adds usage guidance: 'SR-Nummer mit Punkt trennen (235.1)' and an example. Despite 0% schema coverage metric, description compensates well.

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?

Description clearly states it retrieves a federal decree by SR number and lists the details (title, abbreviation, status, etc.). Distinguishes from sibling tools like fedlex_search_laws (which searches) and fedlex_get_law_history (which retrieves history).

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?

Includes explicit <use_case> tag specifying when to use (when SR number is known, e.g., from fedlex_search_laws) and <important_notes> tag with details about repealed decrees and correct format of SR number.

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