load_debt_market

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

With no annotations, the description carries the full behavioral burden. It does disclose useful behavior — what fields are ingested, the destination table, and the 'one `category` per instrument group' grouping semantic — but says nothing about write semantics (insert vs. upsert/replace), permissions, network/data-source requirements, or expected runtime for an ingestion job.

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?

A single dense sentence that front-loads the action, the instrument types, and the destination table. The parenthetical field list is informative rather than filler, though the sentence packs enough clauses that it could be split for readability.

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?

An output schema exists, so return values need no explanation, and with zero parameters there is nothing to document on input. The description covers what is loaded and where, but leaves ingestion preconditions (data source, credentials, overwrite behavior) unstated, which is the only meaningful gap.

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 takes zero parameters, so the baseline is 4; there is nothing for the schema to document and nothing the description needs to disambiguate. The parenthetical list of loaded fields is descriptive context rather than parameter explanation.

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?

States a specific verb ('Load') and a precise resource (PSX debt instruments: TFCs, Sukuks, government securities) plus the destination table `debt_market`. The debt-instrument scope cleanly separates it from sibling loaders like load_prices or load_fundamentals, though the description never names those siblings explicitly.

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 is purely declarative about what gets loaded; it gives no when-to-use condition, no prerequisites (e.g. auth or data source availability), and no guidance on when to prefer it over `query`, `list_tables`, or other load_* tools. The agent must infer its role from the name alone.

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