get_skill_manifest

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered and the description needn't repeat it. The description adds value beyond that by describing the payload contents (capabilities, configuration requirements, interfaces, setup instructions), which matters because there is no output schema. It does not mention size, format, or whether the manifest is static, but the key behavioral facts are present.

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?

Purpose is front-loaded in the first line, followed by what is returned and when to call it — a sensible order with no filler. The middle section is wrapped across several short lines and repeats the resource name slightly, but no sentence is genuinely wasteful.

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 no parameters, no output schema, and safe read-only annotations, the description carries the burden of explaining the return payload and does so adequately. It stops short of telling the agent what to do with the manifest (e.g. how configuration requirements should alter subsequent calls), which would fully complete a self-discovery tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object with 100% coverage, consistent with the description's no-argument framing.

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 opens with a specific verb plus resource ("Get the Kiln skill manifest") and frames it as agent self-discovery, which tells an agent exactly what it returns: capabilities, configuration requirements, interfaces, and setup instructions. It does not name a sibling such as get_started, check_capability, or plugin_info, so the agent must infer the boundary from the 'first connecting' phrasing rather than an explicit differentiation.

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?

It gives a clear triggering condition: "Use this when first connecting to understand what Kiln can do and what configuration is needed," which is a real usage rule rather than restated purpose. It lacks explicit when-not guidance or named alternatives (e.g. versus onboarding or capability-check tools), so it stops short of full routing guidance.

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