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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description adds almost nothing: it does not say what the digest or guide index contains, whether output is paginated or bounded, how large the rule set is, or what changes guide content. The one behavioral hint — that passing a guide reads a single guide — is delivered so tersely it barely counts as disclosure.

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 short, which is good, but it is telegraphic to the point of being cryptic — semicolon-separated noun fragments rather than a front-loaded statement of purpose. Brevity here costs comprehension rather than saving the reader effort.

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?

There is no output schema, so the description must carry the burden of explaining what comes back from a no-argument call versus a guide-scoped call, and it does not. For a tool whose whole value is returning rules and guide content, the agent is left without enough to predict results or choose an invocation.

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 description coverage is 0%, so the schema lists the five enum values (errors, waiting, issue-flow, money, files) with no explanation of what each contains. The phrase 'guide reads one' does tell the agent that the guide parameter selects a single named guide rather than filtering a list, which is meaningful added semantics. It still leaves the meaning of each enum value undocumented, so it only partially compensates.

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 names concrete resources (rules, prohibited tasks, digest, guide index) and hints that a guide is read via a parameter, so the agent can infer this is a read tool for policy/guide content. However, it is a noun-list fragment with no explicit verb and no statement of what the default call (no parameters) returns versus what the guide parameter does. Sibling tools (get_task, search_tasks, get_marketplace_capabilities) are in a different domain, so differentiation is not the issue — self-clarity is.

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?

There is no explicit when-to-use guidance, no statement of when to call this versus search_tasks or get_task, and no note that calling with no arguments yields the rule/digest overview while passing a guide reads that specific guide. The clause 'guide reads one' only weakly implies the selection behavior. An agent must guess the intended invocation pattern.

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