Research a repository

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so this is known to be a safe, repeatable operation. The description adds the behavioral detail that unsupported operations are rejected rather than silently ignored, which is useful but not elaborated in terms of error handling or authorization.

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 contains no filler, but the phrase 'Dispatch admitted research operations and reject the remainder' is stilted and under-specified. It is concise in word count but not structured in a way that clearly separates core purpose from constraints.

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 9 parameters, 0% schema description coverage, and no enums or examples, the description is far too incomplete for an agent to select it and invoke it correctly. The output schema exists, but input semantics are almost entirely undocumented, so the tool cannot be used reliably from this definition alone.

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 compensate by explaining any of the 9 parameters. It only vaguely alludes to 'operations,' but gives no meaning for repository_root, term, path, limit, lines, since_unix_time, or the required operation values, so an agent cannot construct a correct call.

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 title 'Research a repository' supplies a general purpose, and the description adds that only 'admitted research operations' are dispatched while others are rejected. However, 'admitted research operations' is never defined, and the verb 'dispatch' is vague about what actually happens to the repository.

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 usage guidance is provided. There are no sibling tools or alternative routes mentioned, and the description does not explain when an agent should choose this tool or what conditions make an operation 'admitted.' The reader is left to infer the intended usage from the title.

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