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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the concrete return shape (name, summary, record_count, owner/org, and url) and the intended downstream usage, going beyond the structured annotations. No contradiction with annotations.

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?

The description is two sentences, front-loaded with the purpose, and includes return info and next steps with zero waste. Every word earns its place, making it highly concise and well-structured.

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 search tool with three optional parameters and no output schema, the description covers the main use case, return fields, and the recommended follow-up action (query_layer/layer_info). It doesn't discuss result limits or edge cases, but the simple tool scope and strong annotations mean this is sufficiently complete.

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?

The input schema covers all three parameters (limit, query, org_id) with descriptions, giving 100% schema coverage. The description adds context about keyword search and the url output but doesn't elaborate parameter syntax or constraints beyond the schema. Baseline 3 is appropriate since the schema handles parameter documentation.

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 'Search Cumberland County GIS open geospatial datasets... by keyword', identifying a specific resource and action. It also lists the return fields and names the downstream tools query_layer/layer_info, which differentiates its role. This is specific, unambiguous, and distinguishes it from siblings.

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 provides clear context that this tool is for discovering datasets and then instructs 'pass that url to query_layer / layer_info', which implies when to use it. It doesn't explicitly state exclusions or alternatives, but the downstream guidance serves as practical usage direction. This is clear context without formal when-not language.

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