run_schematic_review

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

With no annotations, the description carries the full burden of disclosing behavior. It does not state whether the tool reads, mutates, requires a live session, or returns a report. 'Complete' could imply a state change, but that is speculative, leaving the agent without critical safety or side-effect information.

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, so it is concise, but this is under-specification rather than effective conciseness. It omits necessary context and does not earn its place by providing actionable information.

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?

The tool has one optional parameter and an output schema, but the description gives no information about the purpose, behavior, or when to use it. Even with the output schema existing, the description is inadequate for an agent to select and invoke the tool correctly. The sibling list shows many review tools, but this description does not clarify its unique role.

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?

There is one parameter, 'path', which is optional. The schema provides no description (0% coverage), and the tool description does not mention the parameter at all. The name 'path' offers some intuition, but the description adds no semantic value, failing to compensate for the schema gap.

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 'Complete registered schematic review profile' names a specific resource and an action, but 'complete' is vague. It implies running a review, yet it doesn't explicitly state that the tool executes a schematic review. It is neither a tautology nor fully clear, and it does not differentiate from sibling review 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 provided about when to use this tool versus alternatives like run_testability_review or run_thermal_review. The word 'registered' hints at a prerequisite but does not explain it, offering no explicit or implicit usage context.

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