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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds real value beyond them: partial failures remain explicit, output units and direction convention, and that source/freshness metadata is returned.

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 compact sentences that front-load purpose, then pack units, direction convention, and return shape. Nearly every clause earns its place, though the fragmentation is slightly telegraphic.

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 appropriately discloses return content (data plus source/freshness metadata) and unit conventions. Remaining gaps — behavior on more than five IDs and what 'verified' entails — are minor for a read-only comparison tool.

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 0% and the single parameter is a nested object whose 'spots' field is only a bare string. The description compensates by explaining the format (comma-separated), the cap (five), and validation (verified IDs) — meaningful detail the schema lacks, though the handling of over-limit or unverified IDs is unstated.

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 and resource with scope: 'Compare current conditions for up to five verified comma-separated spot IDs.' The multi-spot, bounded nature implicitly separates it from singular siblings like get_conditions and get_spot, though it never names them.

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 'up to five' and 'comma-separated spot IDs' constraints imply this is the multi-spot batch variant, but there is no explicit when-to-use guidance or exclusion against get_conditions/get_spot for single-spot lookups. Usage must be inferred from scope.

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