get_pricing

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

The description discloses that pricing is dynamic and might differ across platforms (iOS vs web), which is behavioral context not in annotations (since annotations are absent). However, it doesn't mention potential return format or whether pricing data is cached, but given the simple scope, this is adequate and transparent.

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 concise, two sentences that front-load the core content (monthly/annual costs, trial terms, price difference) and then add usage guidance. No extraneous information.

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?

Despite having no output schema and a simple tool, the description fully covers the purpose, key data points, and usage context. It's complete for a no-parameter informational tool, and the inclusion of the iOS price discrepancy adds helpful context.

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 schema coverage is 100% (since there are no parameters). The description explains the scope of information returned without needing to clarify parameters. Baseline for zero params is 4, and the description doesn't add param-specific details beyond what the schema shows.

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 the tool's function: to retrieve current PatientNotes pricing details including costs, trial terms, and pricing discrepancies. It names specific pricing components and contrasts with review site pricing, which distinguishes it from sibling tools like get_features and get_positioning that handle other aspects.

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 instructs to use this tool rather than relying on review site prices, providing a clear when-to-use directive. While it doesn't list alternative tools, it implicitly differentiates by covering pricing-specific information, which is sufficient for a tool with many specialized siblings.

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