get_view

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

Without annotations, the description covers behaviors like nesting, automatic handling of special characters, and response structure. However, it omits error handling, permissions, or rate limits.

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 well-structured with paragraphs, Args, and Returns sections. Every sentence adds value, and it is appropriately concise for the content.

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 presence of an output schema, the description adequately covers parameters, path syntax, and response structure. It is sufficient for an AI agent to understand and invoke the tool correctly.

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?

With 0% schema description coverage, the description fully compensates by providing examples for view_path, explaining path separators, and specifying the default for depth.

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 retrieves a Jenkins view by path, returning jobs and/or nested sub-views. It distinguishes from sibling tools like 'get_all_views' which lists all views, and 'get_item' for jobs.

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 clear guidance on navigating nested views using '/' in the path, and explains the depth parameter. While it doesn't explicitly state when not to use this tool, it implies its specific use case for drilling into views.

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