get_section_subnets

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

With no annotations, the description carries the transparency burden. It discloses the default 20-result limit, the 1000 maximum limit, and the default of essential-only fields in include_fields, which goes beyond the schema. It does not discuss errors, auth, or read-only status, but the get verb and limit details provide adequate 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 description is compact and front-loaded: a one-sentence purpose, a short context note, and a structured Args list. Each line contributes information, and the organization supports both skimming and reference.

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. The description covers all parameters, defaults, and limits, and includes a performance note. It stops short of listing concrete examples or pagination semantics, but is complete enough for a list operation.

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 Args block must compensate. It provides semantic definitions for all four parameters, including defaults and the max for limit, and clarifies that include_fields is comma-separated. This adds real meaning beyond the bare schemas.

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 opening sentence, 'Get subnets within a specific section,' uses a specific verb and resource, and the 'specific section' qualifier distinguishes it from global subnet search and sibling tools such as search_subnets or get_subnet_details. The purpose is unambiguous and not a tautology.

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 when to use the tool—when subnets are needed for a given section—but provides no explicit guidance on choosing among siblings, such as search_subnets for cross-section queries. The 'CONTEXT OPTIMIZATION' note addresses output size rather than tool selection.

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