get_playbook_rules

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

No annotations are provided, but the description clearly states the return content and implies a read-only operation. It does not mention error handling or response format, but for a retrieval tool, the description is fairly transparent about what to expect.

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 concise with two sentences: first states the core function, second provides a usage example. Every word adds value, and it is front-loaded with the key action.

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 simple input (one enum parameter) and no output schema, the description covers the purpose and output content well. It could mention the response structure (e.g., array of rules) or potential errors, but overall it is sufficiently complete for its complexity.

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 100% schema coverage for the single parameter 'category', the description adds no additional meaning beyond the schema description. It simply references 'a given category' without further elaboration.

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 explicitly states the tool returns 'full rule pages for a given category' and details the content (title, description, markdown body, code examples). It distinguishes from sibling tools (get_component, list_categories, list_components) which deal with other entities.

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 provides a clear use case: 'teach a model the exact patterns for a specific concern' and gives an example (responsive layout). It implies when to use but does not explicitly mention when not to use or alternatives, though sibling tool names hint at other purposes.

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