run_typecheck

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

No annotations are present, so the description must convey behavioral traits on its own. It only says 'Run website typecheck' without disclosing side effects, return values, error behavior, or whether the operation is read-only. This is minimal and leaves the agent with little understanding of what happens when the tool is invoked.

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, concise sentence: 'Run website typecheck.' It is front-loaded and contains zero filler, making it efficient and easily scannable.

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?

With zero parameters and no output schema, the complexity is low and the description is minimally adequate. However, it lacks any mention of output format, scope (whole project vs. changed files), or relationship to sibling validation tools, which leaves room for ambiguity in a toolset with many overlapping validation commands.

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 has zero parameters and schema description coverage is 100%, so the baseline of 4 applies. There are no parameter details to document, and the description adds no parameter-specific meaning because none exist.

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 'run' and the resource 'website typecheck', which distinguishes it from sibling tools like run_lint and run_unit_tests. However, it does not explicitly differentiate itself from broader validation tools such as run_all_validation or validate_changed_files, leaving some scope ambiguity.

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 run_typecheck versus alternatives like run_all_validation, validate_changed_files, or run_production_build. The description only states the action without any contextual or exclusionary information.

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