validate_track

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

No annotations are provided, so the description must disclose behavioral traits. It lists validation items but does not state if the tool is read-only, has side effects, requires specific permissions, or what the output contains. The behavior is implied as validation but not explicit.

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 very short and uses a comma-separated list. While concise, it is cryptic and lacks sentence structure. It could be more efficient by explaining the tool's purpose in a phrase rather than a list.

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 4 parameters with 0% schema coverage, an output schema exists but is not described. The description does not cover the return value or behavior. It is incomplete for effective tool selection and invocation.

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?

Schema description coverage is 0%, and the description does not explain any parameters. It does not mention track_path, production, report_path, or trajectory_path. The agent receives no help understanding parameter meaning beyond the schema names.

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 lists multiple validation aspects (schema, chronology, joints, review state, event lock) but does not clearly state the tool's primary function or scope. The verb 'validate' is present but the resource 'track' is implicit. It lacks distinction from sibling tools like inspect_track, which may also validate.

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 on when to use this tool versus alternatives. There are no exclusions, prerequisites, or context indicating appropriate scenarios. The description does not help an agent decide between validate_track and sibling tools.

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