functions_rebuild

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

Discloses no source change, no new release, opt-in nature, auth requirements (wallet-authed only), allowed during billing grace, and lists error scenario (CANNOT_REBUILD_UNLOCKED_DEPS). Covers what happens and prerequisites beyond annotations (none provided).

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 comprehensive but slightly verbose. Each sentence adds value, but could be more concise. Front-loaded with main action.

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?

No output schema, and description does not specify return value or success response. While it covers inputs and side effects, it lacks details on output format, which is a gap for completeness.

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 100%, and description adds value by explaining that omitting name rebuilds all functions and project_id is required. Adds context beyond schema definitions.

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 refreshes functions onto the current entry wrapper and runtime without changing source. It distinguishes from deploy_function and redeploy, providing specific verb and resource.

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 says when to use (to apply gateway-side fixes), when not to use (functions with unlocked deps), and provides alternatives (deploy_function, list_functions, run402 doctor).

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