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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds useful context — that the reference reflects what 'the editor currently knows about' and that references are type-partitioned rather than universal — but says nothing about size, format, or how to detect an unknown type.

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?

Purpose and the script_type instruction are front-loaded and every sentence is load-bearing. The parenthetical per-type details make it denser than ideal, but the content is necessary routing information rather than filler.

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 parameterless-default reference lookup with no output schema, the description tells the agent what each call will return (that type's hooks and context.* namespaces) and how to avoid cross-type confusion. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so baseline is 3, but the description meaningfully enriches script_type by mapping each enum value to a concrete script location and API surface — far more than the schema's one-line default note. scope semantics are largely left to the schema.

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 ('Read the ... local Lua validator/editor reference') and enumerates exactly what it contains (hooks, fields, methods, exact values, handle helpers). It is clearly distinct from siblings such as validate_lua_power_draft or fetch_wiki_page.

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?

Gives explicit routing: 'Pass script_type matching the file you are working on', names each type with the directory/file it maps to, and warns that the boss reference does NOT contain NPC/FMM/Mind/enchantment APIs. The when-to-use condition is spelled out rather than implied.

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