status

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

Beyond the readOnlyHint annotation, the description discloses a concrete failure mode (ok=false with error.code="autocad_not_running") and a side-effect guarantee ("nunca inicia o AutoCAD sozinho"). This is exactly the extra behavioral context annotations do not provide.

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?

Front-loaded with the diagnostic summary, then a clear QUANDO USAR block, then params and example. Dense but every line carries routing or behavioral information; nothing is wasted.

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 parameterless read tool with an output schema, this description covers the full agent decision path: what it inspects, when to call it, and what happens on failure. Nothing needed to call it correctly is 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, so the baseline is 4. The description reinforces this with "Parâmetros: nenhum" and a usage example, leaving no ambiguity about how to invoke it.

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?

Names a specific verb+resource (AutoCAD diagnostic) and enumerates exactly what it reports: connection state, version, active drawing, units, entity count, active command. This lets an agent distinguish it from siblings like list_documents or system_capabilities without opening a schema.

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?

"QUANDO USAR" gives an explicit trigger: first call of a conversation and when suspecting a problem (connection error, "AutoCAD busy"). It states the condition clearly but does not name specific alternative tools or a when-not-to-use case, so it falls just short of 5.

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