Backend Info

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds that this tool provides information about capabilities and available tools, which is useful context, but it does not disclose any other behavioral traits such as whether this is a static snapshot or a live query. No contradiction with annotations exists.

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 a single, front-loaded sentence with no wasted words. It states the action and the target resource clearly and is appropriately sized for a simple, parameterless introspection tool.

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?

Given the presence of an output schema and readOnlyHint annotation, the description is mostly complete for a simple informational tool. However, the lack of disambiguation from system_capabilities and system_status leaves a meaningful contextual gap, since an agent cannot tell which introspection tool is the right one.

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 tool has zero parameters, so the baseline of 4 applies. The empty input schema already confirms no arguments are needed, and the description does not need to add parameter-level detail.

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 clearly names the resource ('AutoCAD MCP Pro capabilities and available tools') and a specific verb ('Get detailed information'), so an agent knows what the tool is for. However, it does not distinguish this from sibling tools like system_capabilities or system_status, which could easily be confused with the same purpose.

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?

The description gives no guidance on when to prefer system_about over similar sibling tools, and it names no alternatives or exclusions. Usage context is only implied by the verb 'Get', which is too weak for a tool family with several introspection-style siblings.

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