hamravesh_app_manifests

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

No annotations available. The description minimally discloses that the tool returns YAML manifests but does not mention read-only behavior, authentication needs, or other behavioral traits. Insufficient for a tool with no annotations.

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 extremely short but underspecified. It is not concise in a helpful way; it lacks critical information, making it inefficient for understanding the tool.

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?

No output schema provided. The description only states the output format (YAML) but does not clarify if it returns a single manifest or multiple, or the structure. Incomplete for a tool with two parameters and no 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?

Schema description coverage is 0%, and the description adds no meaning to the parameters (app_id, org). An agent cannot infer what the parameters represent from the description alone.

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 'Kubernetes manifests of an app (YAML)' is a noun phrase indicating the resource but lacks a verb specifying the action (e.g., get, list). It vaguely conveys the tool's purpose but does not clearly state what the tool does.

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 sibling tools like hamravesh_get_app or hamravesh_list_apps. The description does not provide context for appropriate usage.

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