ntl-team-operations

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what operations can be run without mentioning whether these are read-only, require authentication, have rate limits, or what their outputs look like. For a tool with operations that likely fetch data, this leaves critical behavioral traits unspecified.

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 extremely concise with just one sentence listing the two operations. It's front-loaded with the core functionality, though it could benefit from more detail. There's no wasted verbiage, but it borders on under-specification.

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's complexity (multiple operations with different parameter structures), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't explain what the operations return, how they differ, or provide any context about the Netlify system they operate on, leaving significant gaps for an AI agent.

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%, so the description must compensate, but it provides no parameter information beyond naming the operations. The input schema shows a complex nested structure with 'selectSchema' containing operation-specific parameters, but the description doesn't explain what 'aiAgentName', 'llmModelName', or the operation-specific params mean. Baseline 3 is appropriate given the schema handles structure but lacks semantic explanation.

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 states the tool runs operations 'get-teams' or 'get-team', which provides a basic verb+action combination. However, it doesn't specify what resources these operations act upon (teams from what system?) or how they differ from each other. The purpose is vague but not tautological.

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 is provided about when to use this tool versus its sibling tools (like ntl-user-operations or ntl-project-operations). The description merely lists the available operations without explaining their context, prerequisites, or appropriate use cases.

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