release_pulse

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

No annotations exist, so description carries full burden. It reveals the output is a high-signal summary ranked by market-moving importance and grouped by week. It does not detail response format or potential side effects, but read-only nature is implied.

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?

Three concise sentences: first defines, second gives usage triggers, third contrasts with sibling. 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?

Tool is simple with one optional param and no output schema. Description fully explains purpose, usage, and differentiation. Could mention return format, but 'high-signal summary' reasonably implies a structured digest.

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 covers the single optional parameter with description, range, examples, and default behavior. Description adds no additional parameter semantics, so baseline 3 applies due to 100% schema coverage.

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?

Description uses specific verb 'Returns' and resource 'AU data-release pulse' with clear scope (economic release calendar across ABS, RBA, APRA, AEMO). It explicitly distinguishes from sibling `releases` by noting it ranks by impact and groups by week, making it unique.

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?

Description explicitly names use cases: when asked 'what data drops this week?' or 'when's the next big print?'. It also provides differentiation from `releases` (raw calendar), serving as an alternative guideline.

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