List Company Form Templates

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by specifying pagination behavior (page and per_page parameters, pagination metadata) and the endpoint. It does not contradict 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 two main sentences plus one about the endpoint. It is front-loaded with purpose and compactly includes necessary details (pagination, parameters, API reference), with no wasted words.

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 schema covers all 6 parameters and annotations provide read-only/idempotent context, the description adequately covers usage for listing form templates. It mentions pagination and filters but could elaborate on the response structure or pagination metadata format, though that is not required.

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 has 100% description coverage. The description reiterates that company_id is required and page/per_page control pagination, but adds no new semantic detail beyond what is already in the schema. Baseline 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 the tool returns a collection of Form Templates for a specified Company, with specific use cases (paginated overview, find IDs, filter by query). It distinguishes itself from numerous sibling tools by focusing on company form templates and specifying the required company_id parameter.

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 provides clear usage context: use it for enumerated Forms needing paginated overview, finding IDs, or filtering. It mentions pagination and required parameter. However, it does not explicitly state when not to use this tool or mention alternatives among siblings.

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