audit_connection_conventions

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

No annotations are provided, so the description must convey behavioral traits. It does not indicate whether the operation is read-only, destructive, or requires authentication. The term 'Audit' suggests analysis, but without explicit statement, the agent cannot infer safety or side effects.

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 sentence, which is concise, but it lacks important details about parameters and behavior. It is appropriately sized but under-specified, so it scores in the middle.

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 tool has 2 parameters and an output schema, the description is too brief. It does not explain what the audit produces or how to interpret results. The lack of parameter details and behavioral context makes it incomplete for effective use.

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 input schema has 0% description coverage, and the tool description does not explain any parameters. The meaning of 'environment' and 'limit' is entirely left to the schema's minimal titles, adding no value beyond what is already structured.

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 states the tool's action ('Audit'), resource ('Nango connections'), and purpose ('for suggested MCP tag/metadata conventions'). It effectively distinguishes from sibling tools like 'apply_connection_convention' and 'describe_connection_convention' by emphasizing the auditing aspect.

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 implies using this tool when you want to audit conventions, but it does not provide explicit guidance on when to use it versus alternatives like 'check_environment' or 'describe_connection_convention'. No exclusions or prerequisites are mentioned.

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