List database agent hosts

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the required permission ('database-agent-hosts.read') and the specific fields returned, which are not in annotations. This is complementary behavioral context beyond the structured metadata.

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 two sentences and front-loads the purpose. The first sentence is slightly wordy with the dash and subordinate clause, but it is still concise and informative. Every sentence contributes value.

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 list operation with four optional parameters and no output schema, the description provides enough context: what the tool does, what it returns, and the permission needed. It does not need to explain the detail parameter's size trade-off since that is covered in the schema. Overall, it is complete for correct invocation.

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%, and each parameter already has a clear description (page, detail, search, per_page). The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 verb ('List') and a precise resource ('database agent hosts'), and elaborates with a definition that distinguishes these from generic database hosts. It also mentions the output fields (agent URL, memory/disk budget), making the purpose unambiguous.

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 provides context about what these hosts are, implying when this tool is appropriate, but it does not explicitly name alternatives or exclusions. Given the sibling calagopus_list_database_hosts, an explicit contrast would have been valuable, but the context is clear enough to infer the difference.

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