validate_de_steuer_id

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

Discloses it validates structure only via ISO 7064 check digit, not registration. No annotations exist, but description provides key behavioral details. Could mention return format but not critical for a validation 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?

Three short sentences, front-loaded with imperative 'USE THIS', no unnecessary words. Efficient and clear.

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 simple validation tool with no output schema, description covers purpose, method, and limitation. Missing return value specification but common for such tools; overall complete enough.

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 already describes the 'id' parameter as 11-digit German Steuer-IdNr with ignored spaces/slashes. Description adds context about check digit but not significant extra meaning; baseline 3 is appropriate given 100% schema coverage.

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 the tool verifies a German tax ID (Steuer-Identifikationsnummer / IdNr) and validates its structure using ISO 7064 check digit. It distinguishes from siblings by specifying the exact ID type.

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?

Explicitly says to use before relying on the ID and warns that it does not confirm registration, setting clear boundaries on when to use and limitations.

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