sync_repository

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Trigger re-indexing', which implies a side effect but does not explain consequences (e.g., changes to the index, potential downtime, whether it is asynchronous, permission requirements, or whether it is safe to call repeatedly). This is a significant gap for a mutation-like 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 a single, clear sentence with no unnecessary words. It is front-loaded and directly states the action. There is no fluff, making it highly concise and well structured.

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 simplicity of the tool (no parameters, no output schema) and the absence of annotations, the description provides a basic understanding but lacks contextual depth. It does not explain what happens after the trigger, whether the operation is immediate or queued, or any side effects. For a tool that performs a significant action like re-indexing, more context would aid the agent in deciding when to invoke it.

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 defines zero parameters, and the schema coverage is 100% (vacuously). The description does not need to explain parameters since there are none. According to the rubric, a zero-parameter tool gets a baseline of 4. The description adds nothing about parameters, but nothing is missing either. The additionalProperties: true allows arbitrary extra arguments, but the description does not mention this, which might be a minor 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 clearly states the action ('Trigger re-indexing') and the resource ('the connected repository'). It is specific in that it denotes a refresh operation, which is distinct from the sibling tools that focus on searching and analysis. The verb+resource pattern provides unambiguous intent.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., repository must be connected) or situations where re-indexing would be appropriate. The only implicit hint is 'connected repository', but no explicit exclusions or alternative tool recommendations are given.

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