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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly says 'Shows NCTR lock thresholds, multipliers, and perks' and mentions 'current balance to check tier status and progress to next tier,' making the read-only informational nature clear. It also implies behavior when no target_tier is given ('see the full progression path'), which adds useful behavioral context beyond the schema.

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 and front-loaded with the main purpose. The first sentence covers the core function, and the second specifies the exact details shown. Every phrase earns its place with no redundancy or filler.

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?

This is a low-complexity tool with two optional parameters and no output schema. The description fully explains both usage modes (specific tier or full path) and the kind of information returned (thresholds, multipliers, perks). It is complete enough for an agent to invoke correctly without additional detail.

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%, so the schema already documents both parameters well. The description adds a slight bit of meaning ('target_tier' optionality via 'or see the full progression path' and 'current_balance' for tier status), but it does not significantly enrich the parameters beyond what the schema descriptions provide. Baseline 3 is appropriate.

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 uses the specific verb 'Check' and clearly identifies the resource: 'Crescendo status tier.' It distinguishes itself from sibling tools by naming the specific information it provides (NCTR lock thresholds, multipliers, perks) and offering two clear modes: checking a specific tier or viewing the full progression path.

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 clearly states two usage contexts: checking requirements for a specific tier or seeing the full progression path. It does not explicitly mention when not to use the tool or list alternatives, but sibling tools are sufficiently different that no exclusion is necessary. The optional parameters are not explicitly tied to usage scenarios in the description, but the context is reasonably implied.

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