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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the description is not required to explain the safety profile. It does add two things annotations cannot express: a subscription/entitlement prerequisite ('Subscriber access') and the existence of explicit date-basis and revision semantics, which signals that results carry provenance and can be fetched incrementally. It stops short of describing paging behavior or result envelopes, hence not a 5.

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?

Two short fragments with no filler — nothing wasted. The domain qualifier is front-loaded, but the 'Subscriber access.' sentence fragment is cryptic in isolation and the overall structure is too compressed for a 12-parameter 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?

For a tool with 12 optional filter parameters, an output schema, and four similarly named geopolitical siblings, the description is far too thin. An output schema removes the need to explain return values, but the agent still lacks any statement of what the tool returns conceptually, how filters interact, or how to pick among the sibling tools.

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 100%, so every one of the 12 parameters (as_of, date_basis, after_revision, include_undated, etc.) is already documented in the schema. The description only loosely gestures at date_basis and after_revision via 'explicit date basis and revision history' and adds no syntax, defaults, or interaction rules beyond the schema. 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?

The description is a noun phrase — 'Stored official maritime, sanctions and conflict-zone records' — with no verb stating the operation (query, list, retrieve), so an agent cannot tell whether this returns rows, summaries, or aggregates. It also gives no basis for choosing it over siblings such as geopolitical_event, geopolitical_event_revisions, or geopolitical_event_reaction, all of which sound like they cover the same records.

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 named alternative. The only contextual cue is the fragment 'Subscriber access,' which hints at a precondition but does not tell the agent when this tool is the right choice versus the other geopolitical_* tools.

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