cross_check_news_with_metrics

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

No annotations provided. Description mentions returning time series and filtered news, but does not disclose whether tool is read-only, required permissions, rate limits, or error handling. Adequate but incomplete.

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?

Description is concise (4 sentences) with front-loaded purpose and example. Every sentence adds value; no wasted words.

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?

Tool has 6 parameters and no output schema. Description explains main function and parameter mapping but does not describe output structure, error handling, or edge cases. Adequate for basic use but leaves 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%. Description adds context for topic (mapping to categories) and institution specification (org_code or query), but does not explain parameter formats, constraints, or possible values for other params like news_days, metric_years, news_limit.

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?

Description clearly states the tool cross-checks news claims with public disclosure indicators, gives an example, explains topic-to-metric mapping, and specifies output (time series + filtered news). Distinct from siblings like get_institution_news and get_institution_metrics.

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?

Implies usage for verifying news with data, provides context with example and mapping. Lacks explicit when-not-to-use or alternative tool references, but context is clear enough from sibling list.

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