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

Annotations already cover readOnly, idempotent, and openWorld, so the bar is lower. The description adds genuinely non-obvious behavior: a 300 s public cache with background refresh of stale copies, plus an explicit security warning that provider descriptions are untrusted data.

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?

Three short sentences, front-loaded with the core action, and each sentence adds information an agent cannot get elsewhere (cache timing, refresh behavior, untrusted data warning). Nothing is padding.

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?

There is no output schema, so the description should convey more about what comes back — a list of tool schemas, their shape, or pagination. Combined with zero parameter documentation, the definition is adequate but leaves real gaps.

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 0% and neither of the two parameters (api_key, provider_id) is documented anywhere. The description never mentions parameters or their meaning, so it fails to compensate for the schema gap; only the provider_id pattern constrains input.

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?

States a specific verb (Read) and resource (schemas for reviewed provider tools) and scopes it to reviewed providers. It does not explicitly distinguish itself from close siblings like call_research_tool or list_research_connectors, so the agent must infer the boundary.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named. The agent gets no help deciding between this and call_research_tool or list_research_connectors.

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