Show Company Form Template From Project

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

Annotations already declare readOnlyHint=true, so the description is not required to disclose safety. It adds value by specifying the HTTP method (GET), full endpoint URL, and API category (Project Management > Forms), which aids agent understanding 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 four sentences and front-loaded with the primary purpose. However, it slightly repeats 'Forms' and 'full details', making it a bit redundant but still efficient.

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 show tool with 4 parameters and rich annotations, the description covers the basic context. It includes the endpoint and API reference, but lacks mention of pagination parameters (page, per_page) despite them being in the 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 coverage is 100% and the description only mentions required parameters (id, project_id) and their role as path parameters. It does not add meaning beyond what the schema already provides, so baseline score 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 clearly states it returns details for a specified Company Form Template, using the identifier. It differentiates from siblings such as 'list_company_form_templates' by specifying 'full details' for a single template.

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 says 'Use this to fetch the full details of a specific Forms by its identifier' and lists required parameters. However, it does not explicitly state when to use this tool versus alternatives like 'list_company_form_templates' or provide when-not-to-use guidance.

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