list_subcolumns

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no rate limits, no indication that this is a paginated hierarchical read, so it contributes no incremental behavioral context.

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 single sentence is front-loaded and free of waste, but its brevity comes at the cost of useful content. It is terse rather than efficient, and there is no structure to convey scope or pagination semantics.

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?

Although an output schema exists (so return values need not be described), this tool has 7 parameters including a nested text_offsets/section_offsets cursor scheme and a previous_page fingerprint. A description this short leaves the pagination and detail-level mechanics unexplained, which is insufficient for the tool's complexity.

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 only 43%, and the description says nothing about any of the 7 parameters. Key inputs such as limit, detail (enum summary/full), and offset have no documentation in either the schema or the description, so the description fails to compensate for the coverage gap.

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 verb ("Read") and resource ("subcolumns of a column") are stated, so the basic operation is identifiable. However, it gives no scope, no sense of what a "subcolumn" contains, and no differentiation from siblings like list_columns or list_subtasks. It is barely more than a restatement of the name.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. needing a parent column_id), and no routing to alternatives such as list_columns. The only implied context is that a column_id is required, which comes from the schema, not the description.

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