netlify-user-services-reader

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

Annotations provide readOnlyHint=true, which the description reinforces with '(read-only)'. The description adds minimal context about being a 'read operation' but doesn't disclose any behavioral traits beyond what annotations already provide - no information about authentication requirements, rate limits, response format, or what specific user data is returned. With annotations covering the safety profile, the description adds little 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 brief but inefficiently structured - it's a single run-on sentence that awkwardly combines tool selection guidance with operation naming. While concise, it's not well-structured or front-loaded with the most critical information about what the tool actually does.

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 apparent simplicity (fixed operation with no parameters) and the presence of readOnlyHint annotation, the description is incomplete. It doesn't explain what 'get-user' retrieves, what authentication is needed, or what the response contains. With no output schema and minimal description, an agent would struggle 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?

Schema description coverage is 0%, but the tool effectively has 0 meaningful parameters for the agent - the only parameter is a nested object with a fixed 'operation' value of 'get-user'. The description doesn't explain what 'get-user' means or what user information is retrieved. Since there are no actual user-facing parameters to document, baseline 3 is appropriate, though the description could better explain the operation's purpose.

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 'Select and run one of the following Netlify read operations (read-only) get-user', which is tautological - it essentially restates the tool name 'netlify-user-services-reader' as 'read operations get-user'. It doesn't specify what 'get-user' actually does (retrieve user profile, account details, etc.) or distinguish it from sibling tools like 'netlify-team-services-reader' or 'netlify-project-services-reader'.

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 minimal guidance - it mentions 'read operations' and 'read-only', but offers no explicit when-to-use criteria, no comparison to alternatives, and no context about when this tool is appropriate versus sibling tools. It doesn't explain what user information is retrieved or when to use this versus team or project services.

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