alcove_knowledge_refresh

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only says 'Refresh a topic from active sources', omitting any details about side effects, required permissions, rate limits, or what exactly gets refreshed. This is insufficient for an agent to understand the tool's 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?

The description is a single sentence, which is concise but overly brief. It lacks necessary detail such as parameter explanations or usage context. While it is front-loaded, the brevity harms clarity. It needs more substance to be useful.

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, no annotations, and no schema descriptions, the description is severely incomplete. It does not explain the purpose of each parameter, the outcome of the operation, or how it fits with sibling tools. The output schema exists but is not referenced. The description fails to provide enough context for correct 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%, yet the description provides no explanation for any of the 4 parameters (topic, summary, in_place, workspace). The description only mentions 'topic' implicitly but does not clarify its purpose nor the other parameters. The description adds no value 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 states the verb 'refresh' and the resource 'topic' and mentions 'from active sources', which gives a basic idea. However, it is vague about what 'refresh' entails and does not distinguish it from sibling tools like alcove_knowledge_add_entity or alcove_knowledge_add_note. It is not a tautology but lacks specificity.

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 guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or constraints. This is a complete absence of guidance.

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