NASA Technology Transfer search

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety and idempotency profile is covered elsewhere. The description adds only the auth fact (no API key needed); it says nothing about rate limits, result ordering, or pagination behavior beyond what the schema already states.

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?

One front-loaded sentence that names the resource first, then the collections, then the auth caveat. Every clause carries information, though the parenthetical URL and enumeration make it slightly heavier than strictly necessary.

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 read-only search tool with fully documented parameters and no output schema, the description covers what is being searched and where. Return-shape details are absent but arguably unnecessary, leaving only a small gap around result structure and pagination.

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%, with the enum, default, limit range, and per-parameter descriptions all documented in the schema. The description merely restates the collection options in prose, adding no syntax or format detail beyond the structured fields, so the baseline of 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 gives a specific verb (Search) and resource (NASA's Technology Transfer portfolio), and enumerates the four searchable collections (licensable patents, issued patents, Software Catalog, Spinoff stories). It does not explicitly differentiate from the adjacent sibling nasa_techport, but the licensing/spinoff framing is clear enough for an agent to pick the right 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?

Usage is implied by the collections listed rather than stated: an agent can infer it is for finding licensable NASA technology, software, or spinoff products. There is no explicit when-to-use/when-not or reference to alternatives such as nasa_techport.

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