find_missing_component_fields

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without revealing the return format, side effects, permissions, or whether any modifications occur. The verb 'find' implies a read-only operation, but this is not explicitly stated, and the description does not add value beyond what an agent might infer from the tool name.

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 short sentence, which is economical and front-loaded. However, it omits critical information about parameters and usage, making it more under-specified than appropriately concise. It is not as degenerate as 'Process,' but it fails to earn its place by leaving the agent with unresolved questions.

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 has two parameters, an output schema (though not shown), and no annotations, the description is incomplete. It does not address how path filtering interacts with required_fields, what constitutes a 'missing' field, or the structure of the results. The agent is left with only a vague sense of the tool's full behavior and return contract.

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 input schema defines two parameters (path and required_fields) but includes no per-parameter descriptions. The tool description does not explain the meaning of 'path' or the expected format/contents of 'required_fields,' resulting in 0% schema_description_coverage with no compensating detail. An agent cannot reliably construct the correct argument values from the given information.

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 uses the specific verb 'Find' and identifies the resource as 'components' with the scope 'missing explicit required BOM fields.' This clearly states what the tool does and distinguishes it from write or review tools. However, it does not explicitly mention sibling tools or alternative BOM review functions, so it lacks the explicit differentiation expected for a perfect score.

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 guidance on when to use this tool versus related siblings such as run_bom_review, compare_bom_to_design, or validate_mpn_consistency. There is no mention of prerequisites, exclusions, or complementary tools, leaving the agent without context for correct tool selection.

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