fiscal_guide

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

No annotations provided, so description carries full burden. It clearly describes behavior: returns category summary without parameter, full API list with parameter. No destructive or hidden side effects implied. Lacks mention of rate limits or authentication, but not critical for a guide tool.

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?

Four short, focused sentences. First sentence states main function. Second and third detail parameter behavior. Last gives usage order. No redundant information. Perfectly front-loaded.

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 guide tool with no output schema and one optional parameter, description fully covers what it returns in both cases and how it fits with siblings. No gaps given the tool's simplicity.

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?

Schema already has 100% coverage with enum values and description. Description adds context: without category, returns summary; with category, returns API list. This adds meaningful usage context beyond schema.

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?

Description clearly states that the tool lists 157 OpenAPI items categorized, and specifies behavior with and without the category parameter. It distinguishes from siblings by recommending a usage order (fiscal_guide → fiscal_search → fiscal_query), showing unique role as a guide.

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 states when to use (category summary or full API list) and not to use (data search/fetch, which are for fiscal_search and fiscal_query). Provides a clear ordering recommendation, helping AI agent decide correctly.

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