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

With no annotations provided, the description fully carries the transparency burden. It discloses the credit cost, auth requirement, the qualifying logic (either pathway suffices), the fact that only qualification is reported, and the return JSON fields. This goes far beyond a simple restatement and gives the agent a solid understanding of behavior.

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?

Every sentence in the description earns its place: cost, purpose, methodology, exclusions, prerequisites, and output format are all covered without redundancy. The description is front-loaded with cost and clear purpose, making it efficient despite being detailed.

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's moderate complexity (tax credit qualification with two pathways) and lack of annotations, the description is remarkably complete: it covers eligibility logic, limitations, auth, cost, and expected output fields. No critical selection-driving information appears missing for an agent deciding to invoke this tool.

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?

Although schema coverage is 0%, the description implies that lon and lat identify the renewable energy project site, which adds some meaning beyond the schema's bare 'Lat' and 'Lon' properties. However, it does not specify coordinate format (e.g., WGS84 decimal degrees), ranges, or other parameter details, so the description only partially compensates for the missing schema documentation.

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: 'US Inflation Reduction Act energy community bonus tax credit qualification lookup for a renewable energy project site.' It clearly identifies the tool's purpose and distinguishes it from sibling assess_* tools by focusing on the energy community tax credit. It also details the two qualifying pathways, making the purpose unmistakable.

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 provides clear context for use, including the IRA energy community bonus credit context, prerequisites (Authorization header, 100-credit cost, sufficient balance), and an explicit limitation ('not a project-specific dollar estimate'). It does not name alternative sibling tools or say exactly when not to use it, but the context is strong enough for an agent to select it appropriately.

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