get_nango_auth_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says "Get...information," which implies a read operation, but it does not explain what the information contains, whether Nango must be configured, or what the tool does if authentication is missing. This is minimal and not transparent enough without annotation support.

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 filler. Every word contributes to the meaning, and the length is appropriate for a zero-parameter getter.

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 simple, zero-parameter getter with an output schema, the description conveys the core action and resource. However, it lacks any behavioral context or guidance about what the Nango authentication information represents or when to retrieve it, leaving the agent with only a minimal understanding.

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 there is nothing for the description to add beyond the input schema. Baseline 4 is appropriate because parameter semantics are fully satisfied by the absence of parameters.

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 uses a specific verb ("Get") and a clear resource ("Nango authentication information"). It is not a tautology and is distinct from the sibling tools, though it does not explicitly differentiate itself from any similar-looking tool.

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 word "current" implies this tool is for inspecting the present Nango authentication state, giving some usage context. However, there is no explicit guidance on when to choose this tool over others, nor any mention of prerequisites or configuration requirements.

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