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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds little beyond 'Read' and the vague 'with input references and limits'; it does not explain output shape, pagination, limits behavior, or what the input references refer to. There is no contradiction with the annotations.

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 a single short sentence, which is concise, but it is structurally awkward: 'descriptive funding' is unclear, and 'with input references and limits' is ambiguous. It front-loads the verb but does not communicate clearly enough for the length.

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 tool with one optional parameter, no output schema, and sibling tools that overlap in the research domain, the description should explain what the product parameter does and what kind of analysis output to expect. It provides neither, leaving an agent unable to confidently select the right product value or understand the tool's scope.

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?

There is only one parameter, 'product', and the schema description coverage is 0%. The description never explains what 'product' means, how the enum values (seiche, liquilens, undertow) map to the mentioned analysis types, or why the parameter is optional. The description completely fails to compensate for the missing schema documentation.

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 action ('Read') and a concrete resource ('funding, institution concentration and settlement analysis'), which distinguishes it from the sibling tools that focus on catalog, entities, observations, series, and tracked institutions. However, the phrase 'with input references and limits' is vague and the overall wording is awkward, so it is not a 5.

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 implies the tool is for reading certain analysis types, but it provides no explicit guidance about when to use this tool versus the five siblings, no conditions, and no exclusions. An agent is left to infer usage context from the tool name and the analysis categories.

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