get-netlify-coding-context

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

No annotations are provided, so the description carries full burden. It mentions the tool is a 'required step' but doesn't disclose behavioral traits like what it returns (e.g., configuration data, environment info), whether it's read-only, has side effects, or any constraints (e.g., rate limits, authentication needs). The description is insufficient for a tool with no annotation coverage.

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 two sentences, front-loaded with the key usage instruction, and has no wasted words. It's appropriately sized for the tool's apparent complexity, though it could be more structured (e.g., separating purpose from guidelines).

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It covers usage context well but lacks details on what the tool does, its behavior, or return values. For a tool that seems to provide coding context, this leaves 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?

Parameter count is 1 with 0% schema description coverage, so the description must compensate. The description doesn't mention the 'creationType' parameter or its enum values, failing to add meaning beyond the schema. However, with only one parameter, the baseline is higher, but the lack of param info keeps it at a minimal viable score.

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 should be called when writing serverless or Netlify code, which gives a general purpose, but it's vague about what the tool actually does (e.g., fetch configuration, list resources, provide context). It distinguishes from siblings by focusing on coding context rather than operations, but lacks specific verb+resource clarity.

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 explicit usage context: 'ALWAYS call when writing serverless or Netlify code' and 'required step before creating or editing any type of functions, Netlify sdk/library usage, etc.' This gives clear when-to-use guidance, though it doesn't explicitly mention when not to use or name alternatives among siblings.

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