netlify-team-services-reader

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

The description adds 'read-only' context, which aligns with the readOnlyHint=true annotation, providing no contradiction. It also specifies the available operations ('get-teams, get-team'), which gives behavioral insight beyond the annotation. However, it doesn't disclose other traits like rate limits, authentication needs, or response formats. With annotations covering safety, this adds moderate value.

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 concise and front-loaded in a single sentence, efficiently stating the tool's purpose and operations. There's no wasted text, and it directly communicates the essential information. However, it could be slightly more structured by separating operation details, but it's still highly efficient.

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 under one tool), annotations provide read-only safety, but there's no output schema. The description covers the basic purpose and operations but lacks details on return values, error handling, or how to choose between operations. It's minimally adequate but has clear gaps for a tool with nested operation choices.

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 description doesn't add parameter semantics beyond what the input schema provides. It mentions 'select and run' operations but doesn't explain the 'selectSchema' structure or parameter details like 'teamId'. With schema description coverage at 0%, the description doesn't compensate for this gap. However, since there's effectively 1 parameter (the operation choice), the baseline is appropriate, but no extra value is added.

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 purpose: 'Select and run one of the following Netlify read operations (read-only) get-teams, get-team'. It specifies the verb ('select and run'), resource ('Netlify read operations'), and scope ('get-teams, get-team'). However, it doesn't explicitly differentiate from sibling tools like 'netlify-user-services-reader' or 'netlify-project-services-reader', which likely handle different resource types.

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 usage context by stating 'read operations (read-only)' and listing specific operations ('get-teams, get-team'), suggesting this tool is for retrieving team-related data. However, it doesn't provide explicit guidance on when to use this tool versus alternatives (e.g., 'netlify-user-services-reader' for user data) or any prerequisites. The usage is clear but lacks sibling differentiation and exclusions.

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