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

Annotations already declare a write operation (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot carry: the required authorization scope, infrastructure_networks:write. It stops short of describing failure modes such as duplicate name handling or the consequence of an invalid feature_class reference.

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?

Two short sentences with zero filler: the definition comes first, followed by the hard prerequisite. Nothing is repeated from the title and no sentence fails to earn its place.

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 create tool with no output schema, the description covers identity, meaning, containment relationship, and authorization, which is enough for an agent to invoke it correctly. Minor gaps remain: nothing about the metadata blob or the cardinality/duplication rules, though the 100% schema coverage substantially offsets that.

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 100%, so all six parameters (including metadata's free-form JSON and criticality's enum with its medium default) are already documented in the schema. The description only reinforces two of them ('named' and 'bound to one feature class'), adding no syntax, format, or default information beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb (Create) plus resource (infrastructure network) and then defines the resource itself: 'a named grouping of features bound to one feature class.' That definition lets an agent distinguish it from sibling creates such as create_infrastructure_zone, create_infrastructure_feature_class, and create_infrastructure_asset without opening schemas.

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?

It gives a precondition in the form of a required scope ('infrastructure_networks:write'), which is useful gating, but never says when to choose this tool over the many adjacent create_* siblings or what must exist beforehand at the description level. Usage is implied by the verb rather than articulated.

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