netlify-team-services-reader

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

Annotations already cover readOnly/idempotent/openWorld, so the safety profile is set. The description adds genuinely new context: for get-team and get-team-env-vars only the owning account responds and non-owning accounts surface under notFoundIn, a return-behavior detail not available in the annotations.

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?

Purpose is front-loaded in the first line, and the multi-account paragraph, while slightly repetitive between get-team and get-team-env-vars, earns its place by disclosing routing behavior.

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 read-only selector tool with no output schema, the description covers operation selection and the notable multi-account result routing (notFoundIn). The main gap is that the per-operation params (teamId, envVarKey) are left unexplained.

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 coverage is only 50%, so the description needs to compensate. It does explain the multi-account semantics of the 'account' argument well, but says nothing about teamId or envVarKey and their meaning, so coverage remains incomplete.

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 names the specific operations (get-teams, get-team, get-team-env-vars) and frames the tool as a Netlify team-services reader, so the verb+resource is clear. It does not explicitly distinguish itself from sibling readers like netlify-project-services-reader, but the 'team' scope makes the domain evident.

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?

It gives selection guidance among its own sub-operations and describes multi-account behavior, which helps an agent choose. However, it never states when to use this reader versus the other netlify-*-services-reader siblings, leaving cross-tool selection to inference.

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