get_form

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

No annotations are provided, so the description must fully convey behavior. It only states 'Fetch' implying a read operation, but does not disclose any permissions, rate limits, or side effects. Given the absence of annotations, this is insufficient transparency.

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, short sentence that conveys the core action without unnecessary words. It is appropriately sized for a simple fetch operation, though it could benefit from slightly more detail on what is returned.

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 tool has one parameter and an output schema (not shown but present), the description is somewhat complete. However, it does not clarify the structure of the returned data or any limitations (e.g., pagination). For fetching a form, this is minimally adequate.

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 single parameter form_id has 0% schema description coverage and the description adds no information about it. The schema only provides a title and type, which is minimal. The description should explain the parameter's purpose or format but does not.

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 fetches 'full form metadata, items, and settings,' using a specific verb and resource. It distinguishes from sibling tools like list_questions which only fetch questions, or get_response which fetches responses.

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 implies this tool is for retrieving the complete form structure, but it does not explicitly state when to use it versus alternatives like list_questions or get_response. No guidance on when not to use it is provided.

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