sync_projects

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 discloses the dependency on a session cookie and notes that sync always fetches fresh, but it does not state side effects like whether local changes are overwritten or what the function returns. This is a moderate disclosure level.

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 two sentences long and directly states purpose and usage. Every word earns its place, front-loading the core action and then adding a practical tip. No fluff.

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 simple tool with one optional parameter and no output schema, this description is largely complete: it gives the action, the data source, the auth dependency, and a typical use case. It lacks an explicit note about return values or whether it modifies local state, but for a refresh command, the purpose is self-explanatory enough.

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 100% (the force parameter is documented in the schema). The description adds no additional parameter semantics beyond what the schema already provides. Baseline 3 is appropriate since the schema handles the parameter explanation.

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 uses a specific verb and resource: 'Refresh the project list from your Overleaf account.' This clearly distinguishes it from siblings like list_projects, which likely only lists the already-synced list. The inclusion of 'uses the session cookie' further clarifies the mechanism.

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?

It provides an explicit usage context: 'Run after creating a new project.' This is a clear when-to-use instruction. However, it does not mention when not to use it or name alternative tools, so it falls short of the highest bar.

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