gx3_dead_logic

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

With no annotations, the description carries the transparency burden. It does provide useful behavioral context by stating the xref DB requirement and listing the exact detection categories. However, it does not disclose whether the tool is read-only, what output format to expect, or whether it has side effects, leaving meaningful gaps.

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, efficient sentence that lists detection categories without wasted words. It is appropriately sized and front-loaded, though the missing main verb makes it slightly cryptic and prevents a perfect score.

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?

Despite having only one parameter, the description is incomplete for an agent to invoke the tool confidently. There is no output schema, yet the description does not explain what the tool returns or how to interpret results. It also fails to distinguish this tool from siblings like gx3_lint, leaving the overall context incomplete.

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?

The schema already describes root as 'Extracted project folder' with 100% coverage. The description adds that the tool requires the xref DB, implying the root folder must contain it, which provides meaningful context beyond the schema. This clarification justifies a score above baseline.

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 enumerates specific dead logic categories (constant-off contacts, always-on NC contacts, etc.) but lacks an explicit verb like 'detects' or 'finds.' The tool name implies dead logic analysis, but the description does not clearly state the action, making it only moderately clear and not well differentiated from sibling tools.

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 given on when to use this tool versus alternatives like gx3_lint or gx3_interlock_check. The only usage-related note is 'Requires the xref DB,' which is a prerequisite, not a usage condition. There are no exclusions or alternative recommendations.

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