get_tier_definitions

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

With no annotations provided, the description fully describes the tool's behavior: it returns static definitions without side effects. It adds detail on the returned data elements. While it could mention idempotency or read-only nature, the context of 'get' and 'definitions' implies safety.

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 long, with the first sentence stating the purpose and the second elaborating on outputs and noting no parameters. Every sentence adds value, and the key 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 tool has no parameters and returns tier definitions, the description covers the purpose, output details, and usage note. It is sufficiently complete for an agent to decide when and how to use it, even without seeing the 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?

The tool has zero parameters and the input schema is empty. The description adds meaning by explaining what the tool returns, which goes beyond the schema. There is no need for parameter details.

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 'Get the tier classification system definitions and criteria' and lists specific outputs (tier levels, score thresholds, contract value ranges, pricing flavors, qualifying criteria). It distinguishes itself from more than 30 sibling tools that focus on leagues, fingerprints, and other entities.

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 notes 'No parameters needed,' making the usage context clear. However, it does not provide explicit when-not-to-use guidance or alternative tool comparisons. Given the simplicity of the tool, this is adequate.

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