lookup_neco_data

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds that the scrape is deterministic and free, providing context beyond annotations. No contradictions.

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?

Concise, front-loaded sentences with no wasted words. Each sentence adds distinct value: purpose, output, uniqueness, input guidance.

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?

Covers purpose, inputs with guidance, output fields, and uniqueness. Output schema exists (per context signals). Could mention rate limits or error handling, but annotations compensate. Sufficient for agent decision.

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%. Description adds meaningful guidance: necoUrl is 'most robust', solicitationNumber is 'best-effort', hkey 'improves resolution'. This adds value beyond the schema descriptions.

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?

Description clearly states the verb (fetch and parse), resource (Navy NECO solicitation page), and output fields (solicitation number, title, etc.). It explicitly differentiates from siblings: 'No other govcon MCP exposes NECO data.'

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?

Provides clear guidance on preferred input (full NECO URL) and limitations ('solicitationNumber alone is best-effort'). Also notes it scrapes a public site and is free. Does not explicitly exclude alternatives, but the purpose differentiation suffices.

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