Call any DPF API action (fallback for requests with no dedicated tool)

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

Annotations already provide readOnlyHint=false and destructiveHint=true; the description adds OAuth authentication and the uniform POST+JSON body behavior. However, it does not add much context about the destructive nature, failure modes, or response behavior. It does not contradict the annotations.

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 sentences, front-loaded with the core purpose, and no filler. Every sentence adds either usage guidance or a critical constraint.

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 generic fallback tool with no output schema, the description covers the essential mechanics: path/action/params construction, OAuth auth, workspace scoping, and billing exclusions. It could include a concrete example or error-handling note, but the current coverage is strong for its purpose.

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 100%, so the baseline is 3. The description adds useful framing about the JSON body shape and that params are merged, but it mostly re-states what the schema already documents.

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 clearly states this tool is an escape hatch for calling any DPF API action when no dedicated tool exists. It names the verb+resource (POST to DPF API path) and explicitly differentiates itself from all the sibling dedicated tools.

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 explicitly says to use this tool when there is no dedicated tool, and gives a clear exclusion: billing mutations are not available via MCP and should go through the DPF web UI. This is strong when/when-not guidance with an alternative.

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