Get Configuration

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

Annotations already indicate idempotent and readOnly hints. The description adds that the operation is free and requires no authentication, providing useful context beyond annotations. No behavioral contradictions.

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?

Two sentences efficiently convey purpose, contents, prerequisites, and usage advice. No redundant information; every part adds value.

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 no output schema, the description comprehensively explains what the tool returns, including specific items like jurisdictions, costs, credits, and links. It also covers ordering (call first), prerequisites (none), and integrates well with the sibling tool 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?

No parameters exist, and schema coverage is 100%. The description does not need to elaborate on inputs; it correctly focuses on the output contents and usage context.

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?

Clearly states the tool returns BizVerify's public configuration as readable text, listing specific contents (jurisdictions, costs, credits, etc.). Distinguishes from siblings like list_jurisdictions (which returns only jurisdictions) and verify_business (which performs verification).

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?

Explicitly advises to call this tool first to discover supported jurisdictions and operation costs before verifying, and notes it is free and requires no authentication. This provides clear when-to-use guidance and sets expectations for subsequent operations.

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