get_carry_core_primary_readiness

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 explains the internal logic: combining first-seen policy rates with complete collection heartbeats, rounding evidence start onto the frozen anchor grid, and reporting heartbeat-gap status. This gives a solid picture beyond just saying 'read readiness', though it stops short of specifying side-effect-free guarantees or output details.

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 compact and front-loaded with the core action and resource. The second sentence is dense and packs multiple behavioral details into one long clause, but every clause adds value and there is no redundancy or filler.

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?

The description gives a strong overview of the algorithm, but with no output schema it does not describe what the readiness result contains or how heartbeat-gap status is represented. More importantly, the optional as_of parameter is left completely unexplained, so an agent invoking the tool cannot confidently decide whether or how to set it. These are meaningful gaps for a tool whose only configurable input is undocumented.

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 schema defines one optional parameter as_of with only a timestamp pattern and no description, and the description never mentions as_of or how it influences the result. The parameter name hints at a date, but the description does not explain whether it sets the evaluation time, affects the anchor-grid rounding, or is safe to omit. This is a clear semantic gap.

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 ('Read') targeting a named resource ('frozen carry_core_primary_v1 collection readiness') and explicitly distinguishes itself from chart-manipulating workflows by saying 'without switching a chart'. This is precise and clearly differentiates from siblings like get_oanda_flow_collection_readiness or chart-related 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?

The phrase 'without switching a chart' provides clear context for when this tool is appropriate. However, it does not explicitly mention when not to use it or point to a specific alternative for other readiness or collection checks, so it lacks exclusions.

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