is_root_schematic

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the semantic of checking root vs. sub-sheet status, but does not disclose additional behavioral details such as return format or error handling. No contradiction with annotations; consistent with read-only operation.

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 extremely concise: one sentence plus a parameter doc line. No unnecessary words or repetition of structured fields. It is front-loaded with the core purpose.

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 the tool's simplicity, a single parameter, strong annotations, and the presence of an output schema, the description is complete enough for an agent to understand and invoke it. It could include usage guidance, but that is addressed in the usage dimension, so overall completeness is satisfactory.

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 has no description for schematic_path (0% coverage). The description compensates fully by specifying 'Path to .kicad_sch file' and explaining the default behavior: 'Optional; omit to use the configured default.' This gives clear meaning to the only parameter.

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 clearly states the tool's function: 'Check if a schematic is the root or a sub-sheet.' It uses a specific verb ('Check') and resource ('schematic'), and the focus on hierarchy status distinguishes it from sibling list tools like list_schematic_sheets or get_sheet_info.

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 description provides no explicit guidance on when to use this tool versus alternatives like list_hierarchy or validate_hierarchy. It explains what the tool does and its parameter, but does not mention appropriate contexts, exclusions, or alternative tools.

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