getFormInquiry

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

The description states 'Read-only' and details the return shape, listing specific fields and explaining the effect of the include_raw parameter. Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description adds valuable context without contradicting them.

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, using a clear structure with sections for main purpose, usage condition, required parameter, return details, and cross-reference. Every sentence adds value with no redundant content.

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's simplicity, the description covers all necessary aspects: purpose, when to use, required parameter, return structure, and parameter behavior. Annotations and schema provide complementary info, making the overall context complete for a retrieval tool.

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 description adds meaning beyond the schema by identifying inquiry_id as a path parameter and explaining that include_raw=1 returns raw HTML. Schema coverage is 50% (only include_raw has a description), so the description compensates partially, but could have elaborated on the purpose of each field in return.

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 verb 'Get' and the resource 'Forms Inbox submission', and specifies it retrieves a single item by inquiry_id. It also distinguishes itself from sibling tools by being a read-only retrieval, contrasting with list or mutation tools.

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 explicitly says 'Use when: you hold an inquiry_id from listFormInquiries' and provides a 'See also' reference to the enumeration tool. This guides the agent precisely on when to use this tool and how to obtain the required ID.

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