macaroons_metadata

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

With no annotations, the description carries the burden of behavioral disclosure. It does well by stating the operation is free, requires no payment, and returns specific fields. It could have been more explicit that it performs no purchase or execution, but the 'Get' and 'before purchasing' framing strongly implies a read-only, non-destructive action.

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?

Two tight sentences, front-loaded with the main action and outcome. Every sentence adds value: what it does, what it returns, and that no payment is required. No 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?

For a single-parameter metadata lookup with no output schema, the description provides enough context: when to call it, what it returns, and its cost/behavior. It is sufficient for an agent to select and invoke the tool correctly in the purchase workflow implied by the siblings.

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 100%: the schema already documents target_id clearly. The description adds only the phrase 'feed target' which aligns with the schema, but does not enrich parameter semantics meaningfully beyond the schema. Baseline 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 states a specific verb ('Get'), a clear resource ('metadata for a feed target'), and concrete outputs ('freshness and content_hash'). It also distinguishes itself from purchase-related siblings by explicitly saying it is for 'before purchasing' and requires no payment.

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 gives clear usage timing: use this when you want free metadata 'before purchasing'. It does not explicitly name alternatives or exclusion conditions, but the 'before purchasing' signal is enough to orient the agent relative to siblings like macaroons_purchase and macaroons_execute.

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