iptime_capabilities

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

Annotations already declare it read-only, idempotent, non-destructive, and open-world. The description adds useful behavioral context beyond those annotations by emphasizing that the exposed operation set depends on the actual model and firmware and may differ from the static catalogue.

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?

A single front-loaded sentence communicates the core purpose efficiently. There is no filler, and every word contributes to the tool's meaning.

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 read-only introspection tool with all optional parameters and no output schema, the description conveys the essential return concept: which operations are actually exposed. It is not fully complete because the refresh behavior is unclear, but the annotations and parameter schema cover most of the remaining invocation context.

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 schema already documents domain and router_id with descriptions, so the description does not need to repeat them. However, the refresh parameter has no schema description and the tool description adds nothing about its meaning, leaving a moderate semantic gap.

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 a specific action ('Discover') and a specific resource ('which catalogued operations this model and firmware actually expose'). It establishes the tool's purpose as capability introspection and distinguishes it from simply listing the catalogued operation set.

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 implies the tool is used to check what operations are actually available, but it gives no explicit when-to-use guidance and names no alternatives. The contrasting sibling iptime_list_operations is especially relevant, yet the description does not explain when one should be chosen over the other.

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