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

With no annotations, the description must carry behavioral disclosure. 'Get' implies a read-only query and 'Free' implies no financial side effects, but nothing else is disclosed, such as authentication requirements, rate limits, or whether the value can change over time. For a zero-parameter getter this is mostly acceptable, though not exhaustive.

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 short sentences and every word earns its place. It front-loads the core purpose and adds the 'free' disclosure without unnecessary elaboration or boilerplate.

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?

For a zero-parameter tool with an output schema, this description covers the essential facts an agent needs to invoke it correctly: what resource is being fetched and that no cost is incurred. The only missing contextual detail is when to prefer it over the price-related siblings, but that has already been scored under usage guidelines.

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's coverage is 100%, so there are no parameter semantics to explain. A 4 is the correct baseline because the description is not required to compensate for any undocumented inputs.

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 states a very specific verb and resource: 'Get the current DPYC certification tax rate.' This is immediately distinguishable from siblings like check_price, get_pricing_model, and set_pricing_model, so an agent can identify exactly what this tool returns without opening schemas.

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?

No guidance is given for when to prefer this tool over alternatives, and no context is provided for when it should not be used. 'Free' hints at lower cost but does not explain how this relates to the broader pricing and coverage tools available in the sibling group.

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