list_services_by_category

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true, fully covering the behavioral safety profile. The description adds no new behavioral traits beyond stating it lists services, which is consistent. Thus, the description adds minimal value beyond annotations.

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?

Two sentences: the first states the core function and valid categories, the second provides usage guidance and sibling differentiation. No wasted words, information is front-loaded.

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 the simplicity of the tool (list operation with 3 params, no output schema needed), the description combined with annotations and schema is fully adequate. It tells the agent what it does, how to use it, and when to prefer it over alternatives.

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% with clear descriptions for each parameter including enums for category. The description does not add additional meaning beyond what the schema provides (e.g., the model parameter is already described). Baseline 3 is appropriate as schema does the heavy lifting.

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 action ('List OCI services in a given category') and explicitly lists the valid categories. It also distinguishes from sibling tools by stating it is the 'preferred single entry point that replaces the individual list_*_services tools.' This provides specific verb+resource+scope with sibling differentiation.

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 explicitly states it is the 'preferred single entry point that replaces the individual list_*_services tools,' giving clear guidance on when to use this tool versus the individual list tools. This serves as both context and exclusion of alternatives.

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