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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about what the content is and the ordering rule (read before changing data), but it does not disclose auth requirements, return format, or any behavioral edge cases. Adequate but modest beyond the 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?

Two tight sentences, front-loaded with the core action and its scope. The 'read them before changing data' rule follows immediately. No filler, though it could be marginally tighter.

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 single-parameter, read-only tool with no output schema, the description conveys purpose, content, when to read, and the parameter's condition. It does not describe the shape of the returned instructions/playbooks, but the content is adequately characterized for an agent to invoke it 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?

Schema coverage is 100%, so the `copilot` parameter is fully documented in the schema. The description adds meaning beyond the schema by clarifying the condition under which `copilot` applies ('where the workspace has more than one in-app copilot') and that it selects another copilot's instructions, which the schema states more tersely ('Default: this connection's.').

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?

States a specific verb (Read) plus the exact resource (the workspace's AI-assistant instructions and playbooks) and even enumerates the content categories (house rules, action routing, confidentiality rules). An agent knows precisely what data it retrieves. It does not explicitly name a sibling to distinguish from (e.g., get_automation_docs, list_ai_memory), so it falls just short of 5.

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?

Gives clear when-to-use guidance: 'Read them before changing data,' which tells the agent to consult this prior to mutations. It also explains the conditional use of the `copilot` parameter for multi-copilot workspaces. No exclusions or named alternatives are provided, so 4 rather than 5.

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