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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds minimal context: 'persisted raw responses' clarifies data freshness, but no additional behavioral details like pagination or auth requirements.

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?

Two sentences are appropriately sized and front-loaded with the core action. However, underspecification reduces effectiveness; a bit more detail would improve value without being overly verbose.

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?

With three parameters (one optional) and no output schema or parameter descriptions, the description should provide richer context about usage, return format, and parameter roles. It lacks these essentials, leaving the agent underinformed.

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 description coverage is 0% (no comments on parameters), and the description does not explain any of the three parameters (askId, since, agentToken). The description must compensate for missing schema info but fails entirely.

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 persistent raw responses for a Superforms ask, and provides an analogy to the HTTP bridge endpoint. It distinguishes from siblings like 'get_my_form_responses' enough to hint at different resources (ask vs form).

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?

No guidance on when to use this tool versus alternatives such as 'get_my_form_responses' or 'list_asks'. No exclusions or context provided for the intended use case.

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