get_hansard_currently_processing

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

With no annotations, the description carries the full burden. It discloses that this is a live/current-state read ('currently being processed', 'live updates') and that it returns a list of in-flight items, which is useful behavioral context. It says nothing about refresh cadence, whether results are eventually consistent, or auth requirements, so gaps remain for a no-annotation tool.

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 content is front-loaded, but the pipe-delimited keyword block duplicates information already stated in prose, and the return value is described twice (once inline, once under 'Returns'). Roughly half the text is redundant for a zero-parameter tool.

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?

An output schema exists, so the description needn't explain the return structure in detail, and it still notes the result is a list of in-process items. For a zero-param read tool with an output schema, nothing essential for correct invocation is missing.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There are no parameter semantics for the description to add or omit.

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 a specific verb and resource: 'Get Hansard content currently being processed', with a clear scope ('currently being transcribed or indexed'). It is distinguishable from siblings like search_hansard or get_hansard_sitting_day, though it doesn't name any alternative explicitly.

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?

'Use to check what Hansard content is currently being transcribed or indexed' gives a clear usage context for the tool. It does not state when NOT to use it or point to sibling alternatives such as search_hansard, so it stops short of full routing guidance.

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