lc_preview_set_ai_agent_enabled

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

The description indicates a preview (likely non-destructive) but does not disclose what the preview entails, whether it requires permissions, or any side effects. No annotations compensate.

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 sentence, concise but perhaps too terse. It does not waste words, but more detail could be added without losing conciseness.

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?

Given no output schema, no annotations, and 4 parameters, the description is severely lacking. It does not explain what the preview returns, how to interpret results, or any operational details.

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?

With 0% schema description coverage, the description adds meaning for the 'enabled' parameter by mentioning 'toggling...enabled metadata'. However, the other three parameters (oid, name, token_ttl_seconds) are not explained.

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 states the verb 'Preview toggling' and the resource 'AI agent Hive record's enabled metadata'. It clearly indicates what the tool does and distinguishes it from siblings that perform actual set operations. However, the meaning of 'preview' is not elaborated.

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 guidance is provided on when to use this tool versus alternatives like the actual set operation or other preview tools. The description does not mention prerequisites or context.

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