refresh_project_knowledge

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

Despite no annotations, the description provides key behavioral details: it is a 'safe incremental rescan' that returns a summary. This adequately discloses the non-destructive, read-like behavior.

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?

Three concise sentences: first for purpose, second for usage, third for output. No wasted words. Front-loaded with key action.

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?

For a zero-parameter tool with no output schema, the description sufficiently covers purpose, usage, behavior, and return value. It is complete and leaves no ambiguity.

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?

With zero parameters, the schema coverage is 100%. The description adds no parameter-specific info, which is appropriate. The baseline for no params is 4.

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 ('trigger a safe incremental rescan'), resource ('project sources'), and distinguishes from automatic indexing. It also specifies the return type (summary of changes).

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 indicates this is 'Explicit-use only' and 'Not needed for normal workflow', implying it's for manual override. It does not explicitly list alternatives but contrasts with automatic indexing, which is sufficient.

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