Call any admin (v1) endpoint

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

Discloses mutation (mutates live config), auto-injection of projectId, and destructive nature of delete paths. Annotations indicate readOnlyHint=false and destructiveHint=false, but description adds critical context. No contradiction.

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?

Description is moderately long but well-structured with clear sections: purpose, usage instructions, warnings. Every sentence adds essential information without redundancy.

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?

As a generic tool, providing exhaustive output details is impractical. Description offers references for endpoints and essential safety warnings, making it sufficiently complete for the intended use.

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 has 100% description coverage for all 3 params. Description adds value by explaining path format (without /v1/ prefix) and auto-injection behavior for injectProjectId, beyond what schema provides.

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?

Description clearly identifies the tool as an escape hatch for any /v1 admin endpoint lacking a dedicated tool. It lists example paths and references endpoint indices, making the purpose specific and distinct from sibling 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?

Explicitly instructs to find exact path and body in references, warns about mutation, requires user confirmation, flags 'delete' as destructive, and advises to prefer staging. Provides clear when-to-use and precautions.

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