get_srgplus_guide

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

The read-only behavior is already indicated by annotations, and the description adds context that the tool is an authoritative reference shipped with the connector. No side effects are mentioned, but none are expected; the description accurately represents the operation.

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 concise and well-organized, presenting the tool's purpose and usage guidance in two sentences. It lists the guide's topics without unnecessary detail.

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?

The description fully covers the tool's purpose, content, when to use it, and its availability. For a simple guide retrieval tool, no additional context or caveats are needed.

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 has no parameters, and the schema reflects that. The description requires no parameter explanations, so full marks apply.

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 'Return[s] the full SRG+ how-to guide' and enumerates its contents. It distinguishes itself by being an authoritative reference, a purpose not shared by any sibling tools.

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 description explicitly tells when to use it: 'Call this once before authoring or editing content if you are unsure of the workflow or a widget's shape.' It also clarifies that no separate skill install is needed, removing a potential barrier.

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