NASA TechPort technology projects

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

Annotations already cover readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower; the description adds a genuinely useful operational fact — 'No API key needed' — plus the fact that search results are relevance-ordered. It stops short of describing pagination or rate limits.

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 tightly packed sentence that leads with the resource and its purpose, then enumerates the two modes and the returned data. No filler or redundancy.

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 usefully names the fields a project includes (status, dates, program, TRL, lead org, description, benefits). The only real gap is not clarifying the relationship/priority between query and project_id, which matters for a 0-required-parameter 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 the schema already documents limit, query and project_id including ranges and examples. The description reinforces which fields a single-project fetch returns but adds no parameter syntax or constraints beyond the schema, matching the baseline of 3.

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: search NASA TechPort projects by keyword or fetch a single project by ID, with the fields returned enumerated. It clearly separates the two operation modes, though it does not explicitly differentiate itself from the near-neighbor sibling nasa_techtransfer, which shares the technology-transfer domain.

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 description implies the two modes ('search by keyword, or fetch one project'), which hints at when each parameter is appropriate, but never states that query and project_id are mutually exclusive or what happens if both/neither are supplied. No alternatives or exclusions are named.

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