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

Annotations indicate destructiveHint true and openWorldHint true, but the description adds little beyond that. It mentions 'file changes', 'cloud', 'marketing & strategy' but does not explain what side effects or state changes occur, nor what authentication or rate limits apply.

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 long and lists many sub-actions, but the overall structure is unclear. It front-loads 'Infrastructure: file changes, cloud, marketing & strategy tools' which is too vague to be useful, and the subsequent list is not organized in a way that clarifies the tool's purpose.

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 complexity (multiple sub-actions, open-world schema, destructive behavior), the description is far from complete. It lacks information on what each action returns, error scenarios, and how the 'params' object is used, despite the presence of an output schema.

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 2 params with 0% description coverage. The description provides informal param hints for some actions (e.g., params: {project?, region?}) but does not define valid values for the 'action' parameter or the structure of the 'params' object. This is insufficient for correct invocation.

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 states 'Infrastructure: file changes, cloud, marketing & strategy tools' which is vague and does not clearly define the tool's core purpose. It lists sub-actions but fails to differentiate from sibling tools like nucleus_orchestration or nucleus_governance, all part of the nucleus family.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply enumerates actions without specifying contexts or prerequisites, leaving the agent without decision support.

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