views_push

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

Describes pushing onto a stack, which implies a non-destructive additive behavior. However, no annotations exist, and details like stack limits, ordering, or dismissal are omitted. Adequate but incomplete.

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?

Single sentence with no fluff. Front-loaded with the core action and resource. Every word is necessary.

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?

Sufficient for a simple stack operation given the presence of an output schema. However, lacks usage guidance and behavioral depth, making it only moderately complete.

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% (both parameters described). The description does not add extra semantic value beyond the schema; it only restates 'view' and 'trigger_id' concepts. Baseline score 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?

Description clearly states the action ('Push a view'), the resource ('view'), and the target ('stack of a root view'). Differentiates from sibling tools like views_open, views_publish, views_update that handle views differently.

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 on when to use this tool versus alternatives like views_open or views_update. Lacks context about prerequisites or stacking behavior conditions.

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