Get Table Schema

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

With no annotations, the description must fully disclose behavior. It mentions 'policy-filtered' but does not explain what policies apply, whether the operation is read-only, or any side effects. Lacks details on permissions or error conditions.

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 a single sentence, making it concise and front-loaded. However, it is under-specified; the brevity sacrifices necessary detail, resulting in a mediocre balance between conciseness and informativeness.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It omits return format, pagination behavior (maxColumns), filtering options (schema/profile), and constraints. An agent using this tool would lack critical 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?

Despite 0% schema description coverage, the description only adds meaning for the 'table' parameter (one table). It does not explain 'schema', 'profile', or 'maxColumns', leaving the agent to infer their purposes without guidance.

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 specifies the action ('Return'), the resource ('table columns and types'), and a key qualifier ('policy-filtered'). It distinguishes itself from siblings like ob_describe_table or ob_get_table_ddl by focusing on schema with policy filtering.

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?

No guidance on when to use this tool versus alternatives such as ob_describe_table, ob_get_table_summary, or ob_get_table_ddl. No mention of prerequisites or scenarios where it is inappropriate.

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