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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds real behavioral value beyond them: the returned content must be followed as binding instructions, which shapes how the agent should use the result, and it names the folder-scoped read boundary.

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 sentences, both earning their place: the first defines what is read and what it contains, the second defines when to call it and the obligation to comply. Front-loaded with the resource before the usage rule.

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 output schema, the description usefully enumerates the expected contents (goals, target cost per result, tone, things to avoid), standing in for a return-value spec. It stops short of saying what happens when a client has no instructions, which is the one gap for a lookup 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?

Schema coverage is 100% for the single 'folder' parameter, so the baseline is 3. The description clarifies that the folder is a client folder with an associated instruction set, but adds no naming convention, format, or error behavior beyond what the schema says.

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 and resource ('Read the agency's instructions for one client folder') and enumerates the payload (goals, target cost per result, tone, things to avoid). No sibling tool in the list serves this purpose, so an agent can identify it unambiguously.

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 a clear trigger: call before analysing, writing ads, or changing anything for a client that has instructions. It lacks an explicit when-not or a named alternative, but no plausible alternative exists among the siblings, so the guidance is functionally complete.

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