audit_connection_conventions

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

With no annotations, the description must carry all behavioral disclosure, but it only says 'Audit'. This implies read-only analysis, yet it does not state whether connections are modified, what is actually checked, or what side effects might occur. The presence of an output schema helps structure return values but does not disclose behavior.

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 economical sentence with the verb and resource front-loaded and no filler. It could be more structured about outcomes, but it is appropriately concise.

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?

The tool has only two parameters and an output schema, but the description still omits parameter semantics and usage context. An agent would not know what environment values are valid, what 'audit' checks, or what constitutes a convention violation. This is insufficient for a tool with no annotation support.

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 description coverage is 0%, and the description mentions neither 'environment' nor 'limit'. The schema only provides names and types, so an agent cannot know valid environment values or what the limit parameter controls. There is no compensating detail in the description.

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?

States a distinct action ('Audit') on a specific resource ('Nango connections') with a clear focus ('suggested MCP tag/metadata conventions'). It is distinguishable from sibling tools like build_connection_convention and apply_connection_convention, though it does not define exactly what an audit result looks like.

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 on when to run an audit versus using sibling tools such as describe_connection_convention, build_connection_convention, or apply_connection_convention. There are no exclusions, prerequisites, or alternative conditions provided.

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