subnet_get

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

With no annotations, description carries full burden. It discloses read nature and ETag provision, but does not mention error behavior, authentication needs, or rate limits. Some behavioral context is given, but not comprehensive.

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?

Description is two lines plus argument list, extremely concise and front-loaded with '[READ]' to immediately convey action. Every sentence adds value with no 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?

For a simple get tool with no output schema, description covers input parameters and basic behavior (read, ETag). Could mention error cases or return format, but overall it is sufficiently complete given tool simplicity.

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 coverage is 0%, so description adds necessary meaning. It explains that ext_id comes from subnet_list and target is optional with default behavior. This clarifies usage beyond the schema alone.

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?

Description clearly states it is a READ operation for one subnet by extId, and distinguishes itself from list or create/delete tools by mentioning 'One subnet' and 'ETag surfaced for downstream writes.' It uses a clear verb-resource pair.

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?

Description implies when to use: after subnet_list to get details and ETag. It explains arguments (ext_id from list, optional target). Not explicitly stating when not to use or alternatives, but context is clear for a retrieval tool.

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