ensp_getCampusPlan

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

No annotations provided; description only states what is returned, not behavioral traits such as read-only nature, side effects, or prerequisites. For a tool with no annotations, more context is needed.

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?

Single sentence with no wasted words. Efficiently communicates the tool's action and output.

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, parameterless tool, the description is adequate: it lists key components of the returned plan. Absence of output schema is mitigated by the description's enumeration, though structure details are missing.

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?

Zero parameters; baseline is 4 per guidelines. Description adds no parameter info, but none is needed since schema coverage is 100% and there are no parameters.

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 uses specific verb 'Return' and resource 'built-in eNSP campus network example plan', listing contained elements (devices, links, VLANs, services, NAT, ACLs). Clearly distinguishes from sibling tools that apply, generate, save, or verify configurations.

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 usage when the built-in plan is needed, but provides no explicit when-to-use or when-not-to-use guidance, nor mentions alternatives among sibling tools.

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