nc_linc_search

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

Annotations declare readOnlyHint=true, and the description adds that it searches all datasets and returns metadata. No contradictions. However, it does not disclose pagination behavior, rate limits, or other operational constraints beyond what annotations already convey.

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?

Three sentences: main purpose, return value summary, and cross-reference to companion. Efficient, front-loaded, and every sentence adds value.

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?

Despite no output schema, the description lists the key return fields and links to the companion data-fetching tool. It covers the essential workflow for a simple search tool, though it omits minor details like default limit behavior (already in schema) and search semantics (e.g., exact vs partial match).

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 both parameters (query and limit) already described. The description adds no additional parameter-level details, so it meets the baseline but does not exceed it.

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 clearly states the tool searches across all NC LINC datasets by keyword, specifies the return fields (IDs, titles, descriptions, record counts), and distinguishes itself from the companion tool nc_linc_query by explaining the workflow.

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?

It explicitly instructs the user to use the dataset ID from results with nc_linc_query to fetch actual data, providing a clear when-to-use and how-to-chain with the sibling tool.

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