Get form message templates

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description does not need to repeat that. It adds only 'Body fields: none' and a reference link, which is minimal additional behavioral context. No contradictions with annotations.

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 front-loaded with the purpose, followed by the endpoint and a brief note on body fields and reference. There is no unnecessary wording, and every sentence serves a clear role.

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 tool has a required path parameter (formId) that is unexplained in the description, and no output schema exists to indicate the response structure. The reference link may help, but the description alone is insufficient for an agent to understand the return format or the meaning of formId without external lookup.

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 description does not explain any parameters. The schema documents the query object (with pagination details) but leaves the required path.formId unexplained. With 50% schema description coverage, the description should compensate for the undocumented formId, but it does not, leaving the agent without essential parameter meaning.

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 operation ('Get') and the resource ('form message templates'), and provides the exact API endpoint. It is unambiguous and distinguishes from sibling create/modify operations by the verb, so an agent can identify this as the read tool.

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 gives no explicit guidance on when to use this tool versus the create or modify siblings. It does not mention any prerequisites, exclusions, or alternatives, leaving the agent to infer from the GET verb and endpoint alone.

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