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

readOnlyHint=true already tells the agent this is a non-mutating call, so the bar is lower. The description adds useful context beyond that: the guide covers both request-side UI authoring and reply format, and it encodes an important behavioral constraint about file/photo upload flowing into Taskriz rather than a link field. It doesn't describe the returned guide's size or structure, which is a minor gap.

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?

Three sentences, front-loaded with the core purpose and firing the usage directive early. The parenthetical '(Smalltalk Morphs, laid out by Apple's Human Interface Guidelines with UIKit building blocks)' is dense but earns its place by specifying the technology stack. No 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 zero-parameter, read-only documentation tool with no output schema, the description covers what the guide contains and when to consult it. An agent has enough to decide to call it. The only omission is a hint about the guide's scope or length, which is minor here.

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?

The tool takes zero parameters, so there is nothing the description needs to disambiguate beyond what the schema provides. Baseline for a no-parameter tool applies.

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 subject: guidance on how to author a Taskriz request interface (Smalltalk Morphs following Apple HIG with UIKit blocks) and how the request replies. An agent can tell this is a reference/guide retrieval tool rather than an action tool. It doesn't explicitly say 'returns documentation text', but 'Read it' makes the intent clear.

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?

It gives an explicit trigger: 'Read it before writing a UI for send_request', plus a concrete rule to follow when building that UI (use DocumentPickerMorph/PhotoPickerMorph, never a link field). It stops short of naming alternatives such as check_ui for validation or stating when the guide is unnecessary.

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