pbs_metrics_influxdb_http_get

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

With no annotations, the description carries the full burden. It discloses the read-only nature, crucial token stripping behavior, and the prerequisite PROXIMO_PBS_* config. This provides solid behavioral context beyond the schema.

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 concise and front-loaded with 'READ-ONLY' and purpose in the first sentence. The parenthetical adds a detail about token stripping but is slightly verbose. Overall efficient with no fluff.

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 get operation with an output schema, the description covers purpose, safety, token behavior, and config requirement. It does not mention error cases like missing name, but is otherwise adequate.

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 description coverage is 100%, so baseline is 3. The description does not add new parameter meaning beyond what the schema already provides. It implies the 'name' parameter identifies the server, but no additional semantics.

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 'get one PBS InfluxDB http metric server's config' with a specific verb and resource, and the 'READ-ONLY' prefix emphasizes the safe nature. It distinguishes from siblings like pbs_metrics_influxdb_http_list by specifying 'get one'.

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 does not explicitly state when to use this tool versus alternatives like list or UDP get. While the name and READ-ONLY label imply usage for reading a specific HTTP server config, there is no explicit guidance or exclusion of other tools.

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