bdesign_skill_get

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

With readOnlyHint=true already covering the safety profile, the description adds useful behavior context by specifying what is returned: manifest, compatibility result, and workflow instructions. It also clarifies the skill is 'bundled', which is meaningful information beyond the annotation.

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 a single, efficient sentence that front-loads the core action ('Read') and then packs the key return contents into one line. Every word earns its place; there is no redundancy or filler.

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?

For a simple one-parameter read tool with a readOnlyHint and no output schema, the description provides the essential return-value context: manifest, compatibility result, and workflow instructions. Nothing critical is missing for an agent to call this 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?

There is only one parameter, skillId, and the description's 'one bundled BeatDesign Skill' implies that this ID selects the skill being read. However, schema description coverage is 0%, and the description does not explicitly define where skillId values come from or how the ID maps to the bundled skill, relying mostly on the parameter name and schema pattern.

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 states a specific verb ('Read') and resource ('one bundled BeatDesign Skill'), and names the returned components: manifest, compatibility result, and full workflow instructions. This clearly distinguishes it from sibling tools like bdesign_skill_list by emphasizing 'one' specific skill.

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?

The description clearly implies this tool should be used when you need the full manifest, compatibility result, and workflow instructions for a single bundled skill. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to select it appropriately.

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