netlify-team-services-reader

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, and the description merely restates 'read-only' without adding new behavioral context. It discloses nothing about what the operations return, pagination, or how the optional envVarKey affects results.

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?

A single efficiently front-loaded sentence naming the operation set, with no filler. It is appropriately sized for a thin multiplexer wrapper, though it is arguably too terse to guide use.

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?

With no output schema and a nested anyOf parameter wrapper, the description should clarify what each operation returns and which parameters belong to which variant. It omits all of that, leaving the agent to reverse-engineer operation behavior from schema consts.

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%, and the description adds no meaning for any parameter. It never mentions required teamId, optional envVarKey, or the aiAgentName/llmModelName fields. While the schema's anyOf variants structurally imply required fields, the prose contributes nothing 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 states a specific resource (Netlify team services) and enumerates the three read operations it multiplexes (get-teams, get-team, get-team-env-vars). The name and text distinguish it from user/deploy/project readers, so an agent can tell roughly what it covers, though it never explains how the three sub-operations differ in purpose.

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 says the tool runs one of three read operations but gives no guidance on when to choose each operation, what prerequisites apply, or when to prefer a sibling reader. The agent must infer everything about operation selection from the operation names alone.

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