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

With readOnly/idempotent/non-destructive annotations already covering the safety profile, the description adds genuine value by disclosing the returned content: total principal, issue count, date range, breakdowns by debt type and purpose, and largest/most recent issues. This matters because there is no output schema. It stops short of noting anything about resolution failures or result limits.

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 front-loaded with the scope and return contents, then closes with representative questions. It is somewhat long but every sentence carries information; the sample questions are the only arguably expendable part.

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 four-parameter, read-only, no-output-schema tool, the description adequately covers scope, issuer types, and return shape, and the schema covers all parameters. Minor omissions (pagination, behavior on unresolved issuer names, result size) are not critical for correct invocation.

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 description coverage is 100%, so all four parameters are already documented in the schema, including the sold_status default of both values. The description adds no syntax, format, or edge-case detail beyond what the schema provides, so the baseline of 3 applies.

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 names a specific verb+resource (borrowing history for one California municipal bond issuer) and enumerates the eligible issuer types (city, county, school district, water agency, JPA, state agency). It is clearly distinguishable from siblings like ca_debt_search_issues and ca_debt_statewide_totals, which operate at different scopes.

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 sample questions ('how much has this school district borrowed', 'when did this agency last come to market') give concrete conditions for use and imply a single-issuer profiling scenario. However, it never names the sibling alternatives (e.g. ca_debt_search_issues for cross-issuer lookups or ca_debt_resolve_issuer for name resolution), so exclusions are left to inference.

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