describe

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

The description discloses the underlying SQL command (PRAGMA table_info), indicating a read-only introspection behavior. It does not mention error handling (e.g., for non-existent tables) or permissions, but given no annotations, the description sufficiently conveys the tool's safety profile.

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 sentence that is precise and frontloaded with the core purpose, followed by the technical detail in parentheses. No unnecessary words or redundancy.

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?

The tool is simple with one parameter and an output schema. The description fully explains what the tool does and how it works (via PRAGMA table_info). No additional context is needed 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 0%, so the description must add meaning. It clarifies the 'table' parameter as the name of the SQLite table to describe, which is evident from the tool's purpose. This goes beyond the bare schema definition.

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 clearly states the verb 'describe' and the resource 'structure of a SQLite table', with the specific implementation detail 'PRAGMA table_info'. This is distinct from sibling tools like 'execute' (runs arbitrary SQL) and 'list_tables' (lists table names).

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 implies usage by stating what it does, but it does not explicitly specify when to use this tool over alternatives like 'query' or 'list_tables'. No 'when not to use' guidance is provided, leaving the agent to infer the context.

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