Manageprofiles

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

No annotations are provided, so the description carries the full burden, and it discloses almost no behavior. It does not mention that the delete operation is destructive and irreversible, what permissions are required, or that cursor implies pagination for list. The profile-domain explanation is context, not behavioral disclosure.

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?

Three short sentences, front-loaded with the purpose and followed by domain context and the cross-tool dependency note. Nothing is padded, though the brevity comes at the cost of substance.

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?

An output schema exists, so return values needn't be explained, but for a multi-operation CRUD tool with no annotations and zero schema coverage the description is far too thin. It omits operation-specific requirements (name for create, profile_id for get/update/delete) and any warning about the destructive delete path.

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% across four parameters, and the description only obliquely explains profile_id. The operation enum's five values, the name parameter, and the cursor parameter are entirely undocumented in both schema and description, leaving the agent to guess which parameters apply to which operation.

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 resource is named specifically (NextDNS profiles) and the description explains what a profile is, which is genuinely helpful. But the verb is the generic 'manage' and the fact that this tool multiplexes five distinct operations (list/create/get/update/delete) is never surfaced, so an agent cannot tell what it actually does beyond 'profile things'.

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 line 'Most other tools require a profile_id from this tool' is a real workflow hint that implies list/get should come first to obtain an ID. Beyond that there is no guidance on which operation to pick, when not to use it, or how it relates to manageSettings/manageLists which presumably operate on the same profiles.

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