mobilepush_setup_fcm

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

Annotations are entirely absent, so the description carries the full disclosure burden. 'Set up' hints at mutation but nothing is said about what files are written to the project directory, whether credentials beyond `api_key` are needed, or whether the setup is reversible or destructive.

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 single sentence is short and front-loaded, but this reads as under-specification rather than genuine concision. There is nothing more than a bare phrase, which fails to earn the brevity because it carries almost no decision-relevant information.

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?

A setup tool that writes to a project directory and handles credentials needs to explain prerequisites, side effects, and expected outcomes. With no annotations and no output schema, the description is the only source of context and it is nearly empty, leaving an agent unable to predict what the tool will change.

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 coverage is only 50%: `api_key` has no description, and the tool description never mentions either parameter. The `api_key` is a sensitive value whose source, format, and role in the FCM setup are left entirely unexplained, so the description does not compensate for the schema gap.

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?

States a specific verb ('Set up') and a clear resource ('Firebase Cloud Messaging'), so the broad intent is understandable. However, it doesn't distinguish itself from the sibling `push_setup_fcm`, which appears to target the exact same resource, and 'set up' leaves the actual scope (config files, credentials, scaffolding) unspecified.

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 no guidance on when to use this tool versus alternatives. This is especially costly given the near-duplicate sibling `push_setup_fcm` and related mobilepush tools (`mobilepush_add_handling`, `mobilepush_add_deep_linking`) — an agent has no basis to choose among them.

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