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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully explains that expand_skills=true resolves tool_recipe.skills into returned steps_md/content_md and notes equivalence to the background runner. It does not mention failure behavior, read-only guarantees, or error cases, but 'fetch' implies a non-mutating operation.

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 compact and efficiently structured: one sentence for the primary action and one for optional behavior. No words are wasted, and the most important information is front-loaded.

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?

The description provides enough to invoke the tool correctly for a basic fetch, and the output schema covers return structure. However, the ambiguity between 'procedure' and 'playbook' terminology, especially given the sibling memory_playbook_get, leaves contextual completeness incomplete without additional disambiguation.

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%, so the baseline is 3. The description adds only marginal parameter insight, mainly clarifying the expand_skills effect by naming the returned fields and referencing the background runner. This is helpful but does not substantially extend the schema's already complete parameter descriptions.

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 and resource: "Fetch a stored playbook by name (and optionally version)." This clearly identifies the tool's core function. However, it calls the resource a "playbook" while the tool name is procedure_get and a sibling memory_playbook_get exists, which muddies the distinction between procedures and playbooks.

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 implies when to use the tool: when you need to fetch a stored playbook by name and optionally a version. It also gives parameter-level guidance about expand_skills. However, it provides no explicit exclusion or comparison against the near-identical sibling memory_playbook_get, leaving tool selection partly to inference.

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