search_ntp_time_servers

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds pagination behavior but does not disclose details like whether all NTP servers are returned, default sort order (though that is in the schema), or any special response handling. It adds some value but not rich behavioral context.

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 concise: 'Search NTP time servers with pagination' — a single sentence that is front-loaded with the action and resource, and wastes no words. It is appropriately sized for a simple search tool with fully documented parameters.

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?

Given that an output schema exists and the tool has only three optional, self-explanatory parameters, the description is largely sufficient. However, it could benefit from mentioning that it lists all NTP time servers (since there are no filter parameters besides pagination) and that it complements 'manage_ntp_time_server' for lookups before edits. Still, for a simple paginated list, the current description is nearly 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?

Schema coverage is 100% since all three parameters have descriptions in the input schema. The tool's description does not add any parameter-specific information beyond what the schema provides, but it reinforces that pagination is a feature via 'with pagination'. Baseline 3 is appropriate because the schema carries the explanatory burden.

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 searches NTP time servers and includes pagination, which is a specific verb+resource+scope. It distinguishes from 'manage_ntp_time_server' (which implies create/update/delete) and 'get_ntp_settings' (which likely retrieves configuration), though it doesn't explicitly address these sibling relationships.

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 is given on when to use this tool versus alternatives. It does not mention that this is for listing/looking up NTP servers before modifying them via 'manage_ntp_time_server', nor does it note any exclusions or prerequisites. The sibling tool names imply context but the description itself provides no usage direction.

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