Parse ASN.1

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

No annotations provided. Description indicates parse operation with no mention of side effects, authorization needs, or destructive actions. It is assumed to be read-only, but not explicitly 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?

Single sentence, no redundancy. Every word adds value: specifies input formats and output type efficiently.

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 6 parameters and no output schema, description covers purpose but lacks detail on error handling, return structure nuances, or limitations. Adequate for a common parse task but not exhaustive.

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 covers 100% of parameters. Description adds context about 'auto' detection but does not go beyond schema definitions for other parameters like maxDepth or includeRawValue.

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 verb 'Parse', resource 'ASN.1', and specific input formats (DER, BER, PEM, HEX, base64) that distinguish it from sibling tools like 'normalize_asn1_input' or 'summarize_asn1'. Also specifies output as a JSON tree.

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 guidance on when to use this tool versus alternatives. While the description implies it is for converting ASN.1 text to JSON, it does not discuss scenarios like needing to extract nodes or validate schemas where siblings might be more appropriate.

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