Show Company Form Template

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety. The description adds that it returns a JSON object and mentions the GET endpoint, which is consistent. However, it does not disclose response structure or any additional behavioral traits beyond 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 short (3 sentences) and front-loads the main purpose. It includes endpoint details which may be slightly extraneous but do not significantly bloat the text.

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?

Given the absence of an output schema, the description should provide more details about the returned object structure. It only says 'Returns a JSON object describing the requested Forms' without specifics. Additionally, the inclusion of page/per_page parameters for a single-resource fetch is not explained, potentially causing confusion.

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 coverage is 100% with clear parameter descriptions. The description only restates the required parameters without adding extra meaning or context beyond what the schema already 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?

Description clearly states it returns details for a specific Company Form Template (verb+resource). It distinguishes from list endpoints by specifying 'by its identifier', but does not explicitly contrast with sibling tools like show_company_form_template_from_project.

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 indicates when to use (to fetch full details of a specific form by ID) and lists required parameters, but lacks explicit guidance on when not to use or mention alternative tools (e.g., list_company_form_templates).

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