create_config

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

Despite the name 'create_config', the description accurately states it returns a template, indicating it is a read-only operation. No annotations exist, but the description adds behavioral context about its non-destructive nature and the recommended workflow.

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 main purpose, and every word contributes meaning. No redundancy or wasted text.

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 simplicity (no parameters, no output schema), the description is complete: it explains what the tool returns, when to use it, and what to do next. It adequately equips an agent to invoke it correctly.

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?

The input schema has no parameters, and schema coverage is 100%. The description adds meaning by explaining the tool returns a template for the config file structure, which goes beyond the empty schema.

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 the tool 'Returns a template showing the required structure of the firebase-mcp.json config file'. It distinguishes from siblings by explicitly mentioning reload_config for loading after creation, and implies get_config for reading the current config.

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 specifies when to use: 'Use this when no config file has been found'. It also provides the next step to call reload_config. While it doesn't explicitly exclude other use cases, the context is clear and actionable.

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