getInfrastructureDetailsView

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Discover new devices' which is vague and does not confirm if this is a read-only operation, what side effects exist, or what the return data looks like. The description fails to add behavioral context beyond the tool name.

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 extremely short but at the expense of clarity. The phrase 'Category: Discover new devices' is misleading and not front-loaded with the core purpose. Every sentence should be informative, but here the description under-specifies and wastes space with a redundant category header.

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?

With no output schema and no annotations, the description should compensate by explaining the return format, scope, or relationship to related tools. It does not; the tool remains opaque. For a tool with 3 parameters (including host and apiKey for authentication), this is inadequate.

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 100% with all parameters described. The description adds an example for categoryName but essentially repeats the schema's example. It provides no additional meaning for host or apiKey beyond what the schema already contains, so baseline 3 is appropriate.

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 description states 'Discover new devices on the network' and references a category name, but the tool name 'getInfrastructureDetailsView' suggests retrieving details of an infrastructure view. The purpose is unclear whether it lists new devices or returns details for a given category. It does not differentiate from siblings like listDevices or getDeviceSummary.

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?

No explicit guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusion criteria. Sibling tools such as listDevices and getDeviceInfo are not compared or distinguished.

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