get_effective_rate_profile

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

No annotations provided, so description carries full burden. States it auto-detects from Cost Explorer or CUR with no manual input. Lacks disclosure of potential side effects, authentication requirements, or rate limits. However, zero parameters and simple read-like operation mitigate concerns.

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?

Concise with a clear summary line, detailed explanation, usage context, and relevant examples. Every sentence adds value. 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?

Adequately covers purpose and behavior for a zero-parameter tool. Mentions data sources (Cost Explorer, CUR) and what it captures (EDP, MOSA, negotiated rates). Could mention return format, but not required given no output schema.

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?

No parameters in schema; description explains tool behavior without relying on parameters. Baseline 4 as no additional parameter info is needed.

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 auto-detects effective private rates by comparing billed amounts to public prices. Specific verb (auto-detect) and resource (effective rate profile). Distinguishes from siblings like get_commitment_analysis or get_savings_summary by focusing on rate detection.

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 example queries and mentions internal use cases (commitment optimizer, PR cost estimator). Implies usage for understanding discount size but lacks explicit when-not-to-use or alternatives. Does not directly distinguish from sibling tools.

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