netintel_normalize

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

With no annotations, the description carries the full burden, and it does disclose real behavior: it runs on Claude Haiku, renames keys, coerces types (string→number, "true"→boolean), and fills missing fields with null. It does not cover failure modes (uncoercible values, ambiguous key matches), permissions, rate limits, or whether the model may hallucinate fields — notable gaps for an LLM-backed transformation 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?

Front-loaded with the core action and the mechanic list, which is good structure, but the single sentence is truncated mid-clause ('the exact shape the caller…'), leaving it incomplete rather than tight.

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 2-param, LLM-backed transform with no output schema and no annotations, the description explains the transformation well but omits parameter format details and error behavior, and its final clause is cut off. Adequate but with clear gaps.

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 0% for two required parameters, so the description must compensate. It implies 'data' is the messy input and 'schema' is the target, but never states that data is passed as a string or what the schema object's format/keys should be — the nested-object schema parameter is left essentially undefined.

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 (conform/normalize JSON to a target schema) and enumerates the concrete mechanics: key renaming, type coercion, and null-filling. It distinguishes itself from nearby tools like netintel_json or netintel_text_to_json by framing itself as schema-conformance rather than generic parsing, though it never names a 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?

There is no when-to-use vs when-not-to-use guidance and no named alternative, despite a crowded neighborhood of schema/JSON siblings (netintel_schema, netintel_schema_map, netintel_schema_parse, netintel_text_to_json, netintel_convert). Usage is only implied by the word 'messy or inconsistent'.

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