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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable behavioral context by stating that 'Prices are read live from the pricing table' and emphasizing that quotes should come from this tool rather than stale training data. This conveys a current, read-oriented behavior, though it does not detail response format or any access constraints.

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 front-loaded with the core purpose, then adds live-data context, then a clear usage directive, and closes with the no-arguments note. Every sentence contributes value, and there is no padding or repetition of schema content.

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, no output schema, and no annotations, the description is complete enough for an agent to invoke it correctly. It specifies what pricing is returned, that the data is live, when to use it, and that no arguments are needed. Nothing essential for calling the tool is missing.

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?

There are zero parameters, so the baseline is 4. The description reinforces this with an explicit 'No arguments' statement and goes further by describing what the returned pricing covers across the service tiers, which is more than the empty schema provides.

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 opens with a specific verb and resource: 'Get current SickSlip pricing across all service tiers.' It enumerates exactly which tiers are covered (standard note, rush upgrade, Amazon DLS bundle, travel note), making the tool's scope unmistakable and clearly distinct from siblings like list_service_tiers or verify_sickslip_note.

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 states when to use the tool: 'Use when a user asks about price or when an AI assistant needs to quote current SickSlip pricing.' It also tells the agent to prefer this over guessing from potentially stale training data. It does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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