Nudge Model Pitch Down

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

With no annotations, the description carries full burden. It discloses the incremental nature ('relative to current rotation') and the automatic state refresh, which is a key behavioral trait. However, it does not mention any side effects, permissions, limits, or what happens if degrees exceed physical bounds.

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?

Two sentences, each serving a purpose: first states function, second adds behavioral detail. No wasted words, front-loaded with core 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?

Given the simple tool (1 optional param, no output schema, no annotations), the description covers the essential: purpose, direction, incremental adjustment, and state freshness. It lacks range limits or examples, but is reasonably complete for a nudge operation.

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 description coverage is 100% (the parameter 'degrees' has a description and default). The tool description adds no additional parameter information beyond that, meeting the baseline score of 3.

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?

Clearly states the action ('adjust the model pitch (X axis rotation) downward relative to current rotation'), specifying the resource (model pitch) and direction. Distinguishes from sibling 'nudge_model_pitch_up' by the direction component.

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?

Provides useful context about automatic fresh state query, implying usage when accuracy matters after manual interaction. However, lacks explicit guidance on when to use this tool over siblings (e.g., 'nudge_model_pitch_up') or when not to use it (e.g., if absolute rotation is needed).

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