get_production_context

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, and the description adds meaningful context: it writes to a persistent private artifact, returns a bounded overview plus contextRef, and explicitly performs no model call and no Live edit. It does not clarify artifact lifetime or whether repeated calls replace versus create separate artifacts, but the core side-effect profile is well covered.

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 tight sentences: the main capture-and-return behavior is front-loaded, and the second sentence efficiently rules out model calls and Live edits. Every clause carries 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?

With an output schema present, the description need not explain return values, and the single documented parameter plus rich annotations mean the call mechanics are clear. It leaves some ambiguity about when to use this versus sibling context tools and how long the private artifact persists, but it is otherwise sufficient for correct invocation.

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?

There is only one parameter, projectId, and the schema already documents it as the private project namespace at 100% description coverage. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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 a specific action and resource: capture Live selection and musical context into a persistent private artifact, then return an overview and contextRef. It clearly distinguishes itself from tools that edit Live or invoke a model, but does not explicitly differentiate from other context-getter siblings such as get_selection_context or get_song_musical_context.

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?

Usage is implied by the need for a persistent private artifact of consistent selection plus musical context, rather than stated as an explicit when-to-use rule. No alternatives or exclusions are named, so an agent must infer when this is preferable to another context tool.

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