trawl_sync_sources

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

With no annotations, the description carries the full burden for what is clearly a mutating, network-touching operation. It hints at external side effects ('pull latest from git repos') but never says whether it overwrites local state, whether it is idempotent, whether credentials are required, how long it may run, or what happens to sources that fail to pull. For a write/sync tool with zero annotation coverage this is a substantial gap.

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?

A single short sentence with the operation front-loaded and no padding. The trailing 'etc.' weakens it, and the 'client' phrasing is a concision-induced defect, but structurally it is efficient and readable.

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?

A mutating sync tool with no annotations, no output schema, an underspecified required parameter, and an undifferentiated sync sibling must explain far more than one sentence. An agent cannot tell what gets synced, whether it is safe to run repeatedly, or what it will get back.

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?

Coverage is nominally 100%, but the schema's own text is just 'Pool name' — content-free. The description's only parameter reference is 'for a client', which introduces a client/pool vocabulary mismatch rather than resolving it. The description therefore adds ambiguity instead of meaning.

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?

States a specific verb (sync) and resource (all sources), and the parenthetical clarifies that this means pulling from git repos and similar origins. However, it calls the subject 'a client' while the schema requires 'pool_name', so the agent cannot be certain whether the client/pool identity is the same thing. Sibling trawl_sync_pool is not distinguished from this tool at all.

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?

There is no statement of when to use this versus trawl_sync_pool, trawl_list_sources, or trawl_reindex_pool — all of which plausibly touch the same sources. No prerequisites (connected GitHub via trawl_connect_github, pool loaded via trawl_load_pool) are mentioned.

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