ro_dp_get_guideline

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

The description and tool name convey a read operation, and specifying the target resource helps. However, with no annotations and no output schema, the description does not disclose what the response contains (full text, metadata, etc.) or error behavior.

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?

A single front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and operation.

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 one-parameter getter, this is nearly complete: it names the resource, the lookup key, and the source of that key. The only notable gap is not clarifying whether the returned value is the full document text or just metadata, especially given there is no output schema.

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 100% and the single parameter is already documented with its type and provenance. The tool description adds no parameter-level detail beyond what the schema provides.

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 (Get), resource (ANSPDCP guidance document), and selection mechanism (database ID). This clearly distinguishes it from sibling tools like ro_dp_search_guidelines (search vs. retrieval) and ro_dp_get_decision (guideline vs. decision).

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?

The schema's parameter description identifies the ID as coming from ro_dp_search_guidelines results, implying this tool is used after searching. Context is clear, though there are no explicit exclusions or comparison to alternatives.

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