inventory_remoteconnect_configuration

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

With no annotations, the description carries the full burden and does well: it explicitly states 'never performs unsafe .NET deserialization or modifies the project' and notes that record values are opaque. This provides meaningful safety-related context beyond the name and schema, though it omits other behaviors like path validation or error handling.

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 well-structured: the first sentence states the core purpose and return, while the second adds safety and output characteristics. Every sentence contributes value with no redundancy or filler.

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?

While the description covers the tool's read-only nature and high-level return content, it critically misses the meaning of the required 'path' parameter and any usage context. Since there is no output schema and only one parameter, the description should explain that parameter to be considered complete.

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?

The only parameter 'path' has zero schema description coverage and the description never explains what 'path' refers to, its format, or how it should be provided. The agent is left without any information to populate the sole required parameter correctly.

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 a specific verb ('Read') and resource ('RemoteConnect FDT/DTM topology and configuration-object index'), and clarifies the return value ('every DTM identifier and its InstanceDataRecord groups'). However, it does not explicitly differentiate itself from siblings like list_dtms or inspect_remoteconnect_project, so it falls short of a 5.

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 guidance is given on when to use this tool versus alternatives. Although the description implies a read/inventory use case, it does not state exclusions, prerequisites, or reference sibling tools, leaving the agent to infer selection criteria.

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