get_cost_trending

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

Discloses key behavioral details: supported values for group_by (only namespace), defaults, and optional parameters. No annotations exist to contradict. Could mention read-only nature but not required.

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?

Well-structured with a clear opening sentence and labeled Args section. Slightly verbose but every sentence adds value; no redundancy.

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 no annotations, schema descriptions, or output schema details in context, the description covers all parameters, constraints, and usage context comprehensively. Adequate for an agent to use correctly.

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 0%, but description compensates fully by explaining each parameter's meaning, giving an example for cluster_id, clarifying period defaults, and noting the group_by restriction.

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 the tool retrieves cost trends over multiple time periods for an Ocean cluster. Specifies 'week-over-week or custom period cost changes', differentiating it from siblings like get_cluster_costs or get_savings_summary.

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?

Provides parameter details and defaults, implying usage context. However, lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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