netlify-extension-services-reader

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

The description explicitly states '(read-only)' which aligns with the readOnlyHint: true annotation, providing no contradiction. However, it adds minimal behavioral context beyond what annotations provide - it doesn't explain what data is returned, any rate limits, authentication requirements, or error conditions. The description simply lists operation names without behavioral details.

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 appropriately concise with a single sentence that efficiently lists the available operations. It's front-loaded with the core purpose and wastes no words, though it could benefit from slightly more structure to separate the two operation descriptions.

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 tool with no output schema, 0% parameter description coverage, and no behavioral annotations beyond readOnlyHint, the description is insufficient. It doesn't explain what data the operations return, what 'extensions' are in Netlify's context, or provide enough context for an agent to understand when and how to use this tool effectively.

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?

With 0% schema description coverage and 1 parameter (selectSchema), the description provides no parameter semantics. It mentions operation names but doesn't explain what parameters each operation requires or their purposes. The description fails to compensate for the complete lack of schema descriptions, leaving the agent to infer parameter usage from the schema structure alone.

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 allows selecting and running Netlify read operations, which provides a general purpose (read-only operations on extensions). However, it's vague about what 'extensions' are and doesn't distinguish this tool from sibling read tools like netlify-project-services-reader or netlify-team-services-reader beyond mentioning 'extensions' specifically.

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 provides no guidance on when to use this tool versus alternatives. It mentions two specific operations but doesn't explain when to choose get-extensions versus get-full-extension-details, nor when to use this tool versus other Netlify read tools like netlify-project-services-reader or netlify-deploy-services-reader.

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