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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description only needs to add new context. It adds that OFR has no live search API and this is a static name/mnemonic lookup table, which is useful behavioral context beyond the annotations. It does not describe response/pagination behavior, but that is a minor gap here.

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 sentences carry the entire value proposition, with the core 'browse the full catalog' action front-loaded and the non-live caveat placed at the end. There is no filler or repetition that dilutes the guidance.

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 simple optional-parameter lookup with no output schema, the description covers the main contextual needs: what is searched, why an agent would use it, and how it relates to companion data/anomaly tools. It could name the return shape, but the catalog/browse framing and downstream tool references make the behavior sufficiently clear.

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%, so the schema already documents all three optional parameters. The description's query examples and downstream usage context add purpose, but they do not materially extend the parameter semantics already present in the schema; baseline 3 is appropriate.

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 names a specific verb ('Browse the full catalog') and resource ('OFR repo-market and money-market-fund mnemonics'), gives concrete query examples, and distinguishes itself from the sibling data tools by saying it finds series behind ofr_repo_rates/ofr_mmf_holdings or a mnemonic for ofr_funding_anomaly. It is immediately clear what this tool is and what it is not.

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?

It explicitly tells the agent when to use it ('to find the exact series behind ofr_repo_rates/ofr_mmf_holdings, or a raw mnemonic to pass to ofr_funding_anomaly') and frames the tool as a lookup rather than a live call. It does not spell out when-not-to-use conditions beyond that non-live distinction, so it falls just short of the top bar.

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