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

Goes well beyond the annotations by disclosing the free-account auth requirement, the two-state screening semantics (match=likely vs check with reasons, plus not_matched reasons), the returned fields (url, apply_url, as_of, stale), and an explicit 'not advice' caveat. This is rich context the structured fields do not provide.

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?

Front-loads the auth requirement, then screening logic, then return values, then disclaimer. Dense but each sentence carries real information; only mildly long.

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?

With no output schema, the description steps in to describe return structure (benefits, amounts, url, apply_url, as_of, stale) and match states. Combined with the auth note, an agent has everything needed to call and interpret it.

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 coverage is 100%, so every parameter is already documented in the schema. The description only loosely echoes country scoping and event types, adding little syntax or format meaning beyond what the schema supplies. Baseline 3 applies.

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 (find) and resource (subsidies / convention-bureau and tourism-board support schemes) scoped to MICE event types. No sibling tool covers subsidies, and the description makes the domain and output framing unmistakable.

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?

Clearly frames the context (an exhibition, conference, meeting or incentive, optionally in one country) and flags the sign-in prerequisite. It doesn't name a competing tool or state when-not to use it, but there is no overlapping sibling to route against.

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