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

With no annotations, the description carries the full burden and does: declares it read-only, discloses the severe shared keyless quota (25/week server-wide), explains the degraded-mode behavior (says so at once with reset time instead of querying), and interprets result semantics. Exceptionally transparent.

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?

Front-loads the primary purpose and result semantics, then the availability caveat. Dense but every sentence earns its place; slightly long but justified by the quota caveat.

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?

A single-parameter, no-output-schema tool, and the description covers purpose, result interpretation, quota failure mode, and host-name handling — everything an agent needs to call it and interpret outcomes correctly.

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%, so baseline is 3; however the description adds meaning the schema doesn't — that host names are accepted and the first resolved IP is used, which explains non-obvious behavior of the single 'target' parameter.

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 (Check) and resource (an IP) and the exact data source (GreyNoise Community) plus what is returned (noise status, classification, scanner name, last-seen time). Unmistakably distinct from siblings like ip_reputation_aggregate or blacklist_check.

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?

Explains what a 'not observed' result means (not an endorsement) and notes host names resolve to the first IP, giving clear interpretation guidance. It does not explicitly route to the ip_reputation_aggregate sibling, but the context is otherwise clear.

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