check_timeline

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add one useful behavioral detail: the result is 'every problem, or none,' indicating an exhaustive error report. However, it does not state whether the tool is read-only, what permissions it needs, or how the problems are formatted, leaving significant gaps for a check operation.

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 extremely short, but it is not a complete sentence and omits essential information for invoking the tool correctly. Its brevity reflects under-specification rather than disciplined conciseness.

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 absence of annotations, output schema, and schema parameter descriptions, the description should carry much more of the context. It communicates the tool's broad intent and a hint about the return value, but is missing usage guidance, parameter clarification, and behavioral details needed for confident 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 single 'path' parameter is undocumented in both the schema and the description. The description mentions 'a timeline file' but never explains what the path parameter should point to or how it is interpreted, so it adds no meaning beyond the schema.

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 identifies the resource (a timeline file) and the contract (feellab-timeline/1), and the tool name 'check_timeline' supplies the verb. It is clear enough for an agent to distinguish from siblings like list_checklist or judge_folder, though the description itself is a fragment rather than a complete statement.

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?

There is no guidance on when to use this tool versus alternatives, nor any preconditions or exclusions. The description only states what it checks, leaving the agent to infer the appropriate context entirely.

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