schematic_summary

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it returns summary information, without mentioning what happens if no schematic is loaded, whether it is a read-only operation, or any error conditions. This is a significant gap for an operation that depends on prior state.

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 with no fluff. It front-loads the action ('Return') and the resource ('summary information') immediately, making it easy to parse. It is appropriately sized for a simple no-argument tool.

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 low complexity, a short description is acceptable. The output schema (present) covers return value details. The description mentions the 'current schematic' which implies a prerequisite, though it does not explicitly state what happens if none is loaded. This is a minor gap for an otherwise simple tool.

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 tool has zero parameters, so per the baseline rule it earns a 4. The description adds context about the 'currently loaded schematic' which hints at a state dependency rather than input parameters. It does not need to explain any parameter meaning since there are none.

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 verb 'Return' and the resource 'summary information for the currently loaded schematic.' It is specific enough to distinguish from sibling tools like list_components or get_component, though it does not explicitly name any alternative. The term 'summary' implies an overview, which is distinct from the detailed queries offered by siblings.

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 gives no guidance on when to use this tool versus the sibling tools. It does not mention that it should be used to get a quick overview or that list_components etc. should be used for specifics. There is no mention of preconditions like needing a schematic loaded first, although 'currently loaded' implies it.

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