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

With no annotations, the description must disclose behavior. It mentions 'offline' as a key trait, but does not explain input format, expected output structure, error handling, or limitations. For a calculator tool, this is a significant gap.

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 extremely short (7 words), but this is under-specification rather than effective conciseness. It omits essential information about the parameter and usage, so it fails to earn its place as a useful definition.

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 simple calculator tool with one parameter, the description should at least specify what the input looks like and what the output contains. It does neither. Even though an output schema exists, the lack of parameter explanation makes the tool hard to invoke 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?

The input schema has one parameter 'q' with no description, and schema description coverage is 0%. The tool description does not explain what 'q' should contain (e.g., a CIDR string like '192.168.1.0/24'). This is a critical omission; the description adds no meaning beyond the schema.

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 states a specific purpose: 'CIDR Calculator: Network/broadcast/host-count (offline)'. It clearly identifies the resource (CIDR) and the computations (network, broadcast, host count). However, it does not differentiate from the sibling tool 'cidr', which likely has a similar function, so it loses a point.

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?

No guidance on when to use this tool versus alternatives. The description does not mention any specific use cases, prerequisites, or exclusions. An agent would not know if this is the right tool compared to 'cidr' or other IP-related tools.

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