functions_rebuild

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

No annotations provided; description covers behavioral traits: no source change, no new release, re-bundles with pinned deps, picks up wrapper fixes, strict opt-in, auth requirements, and error case for unlocked deps.

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 verbose but well-structured, front-loaded with key action, and each sentence adds value. Could be slightly more concise but appropriate for complexity.

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?

Covers action, preconditions, error conditions, and related tools, but does not describe return values since no output schema exists. Comprehensive given tool simplicity.

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% with parameter descriptions. Description adds significant context for 'name' (optionality, batch behavior) beyond what the schema provides, adding clear semantics.

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 wrapper/bundled runtime without changing source, distinguishing it from redeployment and sibling tools like deploy_function.

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 states when to use (wrapper fixes), when not to (unlocked deps, suggesting deploy_function), and provides context (opt-in, wallet-authed, billing grace allowed). Also points to list_functions to find stale functions.

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