ps_fetch_items

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether fetching is idempotent, how deduplication keys are chosen, whether existing raw items are overwritten, or what permissions/rate limits apply. 'Deduplicate' is the one real behavioral hint, which keeps this above a 1.

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 front-loaded sentence with no filler, which is structurally sound. It is under-specified rather than bloated, so the size itself is not a defect.

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 five-parameter tool with zero schema coverage and no annotations, the description omits everything an agent needs to call it correctly - source selection, time window semantics, run scoping. The presence of an output schema excuses it from describing return values but not from the input-side gaps.

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% across five parameters, and the description explains none of them. hours, run_id, sources, config_path, and periscope_path are all opaque from the description; only 'sources' is loosely implied by 'fetch content.'

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 names a verb (fetch) and a resource (content) and scopes it to the 'raw stage,' which hints at its position as the first pipeline stage relative to ps_score_items/ps_enrich_items. However, it never says what content or from where, so it is only loosely distinguishable from sibling ingest-style tools.

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 when-to-use guidance, no preconditions, and no mention of alternatives such as ps_corpus_import or ps_run_pipeline. The agent must infer the pipeline position entirely from the phrase 'raw stage.'

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