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

The annotation provides high-level safety (readOnlyHint: true), but the description adds crucial context regarding the tool's function—a detailed reference and glossary of terms. This adds significant value beyond the annotation's scope.

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 definition is appropriately detailed given the nature of the tool (an 'About' resource). While lengthy, every sentence serves a crucial function in defining the scope and utility of the tool.

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?

As a meta-tool, it is exceptionally complete. It covers data freshness, coverage, terminology, and contact info, which are all essential for a user interacting with the 'radar' source.

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?

Since schema coverage is 100% and there is only one parameter, the description primarily restates or elaborate on the parameter's scope without adding new semantic meaning beyond what the input schema already provides. 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 purpose is explicitly stated as a reference to the Funding Radar source itself. It details the content covered (exchanges, glossary, contacts) and distinguishes it from other 'data 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 instructions are prescriptive: 'Call this when the user asks what this source is, how to interpret a field, where to follow it, or how to reach the team.' It explicitly dictates the boundaries of usage and exclusion.

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