validate_esic_code

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

The description adds no behavioral detail beyond the annotations: '# PermissionTier: READ_ONLY' just restates the existing readOnlyHint, and the annotations already declare read-only and idempotent behavior. It does not disclose any validation side effects, network calls, or edge-case 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?

The description is a single clear sentence that states the operation and resource with no filler. The permission line is minimal and the information is front-loaded.

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, single-parameter, read-only validation tool with an output schema, the description plus schema annotations provide sufficient context to call the tool correctly. No return-value explanation is needed since the output schema exists.

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 schema already covers the one parameter fully, including the required flag and the expected format 'XX-XXXXX-XXXXX'. The description itself adds no additional semantic meaning beyond what the input schema provides, so the baseline 3 applies.

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 'Validate' and a specific resource 'ESIC employer code', so an agent immediately knows the operation and subject. It clearly distinguishes itself from sibling tools like validate_gstin and validate_pan by naming the exact code 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?

Usage is implied rather than explicit: the tool is for validating ESIC employer codes, but the description provides no when-to-use conditions, no exclusions, and no pointers to alternatives. With many sibling validators, more explicit routing guidance would help.

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