bcrp_get_macro_snapshot

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

No annotations are provided, so the description carries the burden. It clearly indicates a read-only fetch operation ('Fetch'), and discloses what data is returned (daily vs. monthly, specific indicators, time spans). It doesn't discuss rate limits or output format, but for a simple read-only snapshot tool, the behavioral context is largely covered.

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 well-organized with a leading purpose sentence, clear bulleted breakdown of daily and monthly indicators, and a final one-line routing hint. Every sentence earns its place, and the structure makes the content scannable.

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 tool has one optional parameter, no output schema, and no annotations. The description compensates well by enumerating the returned indicator groups and values, specifying the monthly lookback period, and naming the sibling for extended use cases. Nothing essential for calling this tool correctly 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 only parameter, language, is fully documented in the schema with its allowed values ('esp'/'ing') and default. The description adds nothing beyond the schema, but with 100% schema description coverage the baseline of 3 applies.

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 opens with a specific verb and resource: 'Fetch a real-time snapshot of Peru's key macroeconomic indicators in one call.' It enumerates exactly which indicators are included, and explicitly names bcrp_get_series as the alternative for custom date ranges, distinguishing this tool from siblings.

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 description clearly states when to use this tool (for a quick snapshot of standard daily and monthly indicators) and explicitly directs the agent to bcrp_get_series for custom date ranges or additional series. This gives concrete routing guidance relative to at least one sibling.

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