Get Organization Doc Template

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

Annotations already mark readOnlyHint=true, and the read-only 'Get' verb is consistent. The description adds useful behavioral context beyond annotations by specifying that the response includes the full content and rowVersion, giving the agent a clear expectation of the output surface.

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 a single, tightly worded sentence with no filler. The verb, resource, and return contents are all front-loaded, making it immediately scannable for an agent.

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 simple one-parameter, read-only get operation, the description is nearly complete: it states what is returned (full content and rowVersion), and the schema handles parameter documentation. It lacks explicit error or edge-case behavior, but that is not critical for this straightforward operation.

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 schema documents templateId with 100% coverage, so the description does not need to add parameter details. The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 a specific verb ('Get'), a precise resource ('one organization documentation template'), and the key return contents ('full content and rowVersion'). This clearly distinguishes it from sibling list_org_doc_templates and other get_* 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?

No explicit alternatives or 'when to use' guidance is provided. The wording 'one ... template' implies this tool is for retrieving a single template as opposed to listing them, but the description does not explicitly route the agent away from list_org_doc_templates.

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