roam_get_guidelines

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

Discloses that it returns `exists:false` instead of failing when no page exists, and returns today's daily note title as orientation. These behaviors go beyond the read-only/idempotent annotations, adding valuable context about response handling.

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?

Four sentences, each serving a distinct purpose: function, invocation timing, differentiation, and edge-case behavior. No fluff; front-loaded with the core purpose.

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?

Despite lacking an output schema, the description fully explains what is returned (conventions, daily note title, exists:false behavior), when to call, and how it differs from related tools. This is complete for the tool's 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?

Input schema already documents both parameters with full descriptions (100% coverage). The description adds only a hint about per-graph configurability, which doesn't materially enhance schema information, so a baseline score of 3 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 clearly states the tool retrieves user-defined agent conventions from a specific page (`[[roam/agent guidelines]]`). It distinguishes itself from `roam_markdown_cheatsheet` by contrasting graph handling conventions vs syntax/mechanics.

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?

Provides explicit when-to-use guidance: 'Call this ONCE per graph per session, before other tools, INCLUDING for reads.' Names the alternative tool (`roam_markdown_cheatsheet`) and explains the difference, giving clear decision criteria.

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