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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds useful context beyond annotations: catalogue size (~1,300 layers), authoritative status, and the specific metadata returned (identifier, human title, resolution grid, image format, date range). No auth or rate-limit details, but annotations cover the safety profile.

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?

Opens with a use-case question, then one dense sentence. The example layer types and return-field list are informative but slightly padded. Overall front-loaded with no major waste.

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?

No output schema exists, yet the description documents the return shape (identifier, title, resolution grid, format, date range). Combined with full schema coverage and safety annotations, an agent has everything needed to call and interpret the 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 description coverage is 100%, so baseline is 3. The description adds no parameter-level detail beyond what the schema provides; it only describes the returned fields.

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 'search NASA GIBS... catalogue', a specific verb over a specific resource, and distinguishes itself by noting it returns the identifiers that the other two GIBS tools consume. An agent can tell this is the layer search/list tool rather than a detail or tile-fetching tool.

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?

Frames the tool as the way to answer 'what layers exist' and indicates that omitting query lists the whole catalogue. It hints that returned IDs feed the other two tools, but does not explicitly name gibs_layer_info/gibs_tile_url or state when not to use this tool.

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