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

Annotations already declare this a safe read (readOnlyHint true, destructiveHint false), so the bar is lower; the description usefully adds that no login is required and that each call costs one token. However, the bulk of the text is generic idempotency-key boilerplate that is largely irrelevant to a read-only, anonymously accessible detail fetch and may mislead an agent into overthinking key management.

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 first two sentences are efficient and front-loaded, but five sentences of idempotency-key policy dominate a one-line read operation, dwarfing the actual purpose. The token-cost note is buried at the end after boilerplate the agent likely doesn't need here.

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?

Auth availability and token cost are covered, and annotations carry the safety profile, but with no output schema the description never indicates what a form detail contains (body text, metadata, attachment references) or that forms__attachments is the route to files. Adequate but leaves real gaps for a detail-lookup 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?

Schema coverage is 100%, so the schema already documents bbs_id and pst_sn with their source (forms.list), and the description adds no field-level meaning. It only expands on request_idempotency_key behavior, which is already referenced in the schema – baseline 3 applies.

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?

States a specific verb+resource ('Get form detail'), which an agent can distinguish from the sibling forms__list and forms__attachments reads. It does not explicitly name those siblings or clarify the boundary, so it stops short of a 5.

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?

There is no statement of when to use this detail fetch versus forms__list (to discover IDs) or forms__attachments (to get files); the list-to-detail workflow only appears in the schema's parameter text, not the description. The only guidance given is authentication availability, which is context rather than tool selection.

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