get_right_sizing

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

Discloses sorting by savings potential (CPU delta), truncation to limit, default values, and parameter defaults; no annotations exist, so description covers behavioral traits well, though authentication requirements or side effects are unaddressed but appropriate for a read-only tool.

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?

One-sentence purpose followed by a clear, bulleted parameter list; no redundancy, front-loaded, and every sentence adds 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?

Given output schema exists, description covers all necessary details: purpose, all parameters, sorting, truncation, and cloud support; no gaps for agent 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?

With 0% schema coverage, description fully explains each parameter including example for cluster_id, optional namespace, account_id with env var fallback, cloud choices, and limit with all-results behavior; adds significant meaning beyond schema.

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?

Clearly states it retrieves right-sizing suggestions for Ocean clusters on AWS/Azure, distinguishing it from other get tools like get_cluster or get_cost_trending.

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 on when to use this tool versus alternatives; does not specify when not to use or mention related tools for comparison.

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