netintel_schema_map

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the deterministic-first strategy and that an LLM is invoked only for semantic mapping, plus support for hints, transforms and defaults — meaningful context. It still omits whether anything is mutated/persisted, determinism guarantees, failure behavior when no mapping exists, and how errors are surfaced.

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?

One front-loaded sentence that leads with the verb and resource before adding mechanism. Efficient, though the trailing ellipsis suggests truncation and the clause chaining (matching + LLM + hints/transforms/defaults) packs several ideas into one breath.

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 7 parameters at 0% schema coverage, no annotations, no output schema, and nested object inputs, the description should define parameter shapes and the return contract. It covers only the broad mechanism and three optional features, leaving an agent unable to construct a correct call with confidence.

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% across 7 parameters, and the description only illuminates three of them (hints, transforms, defaults) plus obliquely allow_llm via 'uses an LLM only for semantic mapping when needed.' The required parameters source/target_schema are only implied, and 'mode' — a free-form string with no enum — is entirely unexplained.

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+resource pair: 'Transform a source object into a target schema,' and adds mechanism detail (alias/structure matching, LLM fallback). It does not, however, differentiate itself from close siblings like netintel_schema_parse, netintel_schema, or netintel_normalize, so an agent cannot route between them from the text alone.

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?

The trailing clause 'so agents can reshape data' implies the usage context (reshaping between differing schemas), but there is no explicit when-to-use, when-not-to-use, or named alternative versus netintel_normalize/netintel_schema_parse. Usage is only inferable.

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