surveys_get_surveys_submissions

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

The description adds no behavioral context beyond the verb 'Get', which is consistent with the readOnlyHint annotation. No mention of pagination, filtering logic, default date ranges, or response format. While annotations cover safety, the description fails to disclose any operational behavior, so the burden is on the schema.

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 extremely short, but it is under-specified rather than concise. It conveys no useful structure or front-loaded information—just a noun phrase. It reads as a placeholder, not a crafted description.

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 7 parameters and no output schema, this description is grossly incomplete. It fails to explain what is returned, how filters combine, or the pagination model. An agent would have to rely solely on parameter descriptions, which is risky for correct invocation.

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 100%, so each parameter (q, page, endAt, limit, startAt, surveyId, locationId) is already well-documented with meaning and defaults. The description adds no parameter-specific context, but given the full schema coverage, a baseline of 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 'Get Surveys Submissions' is essentially a restatement of the tool name. It states the verb and resource but adds no specificity about what 'submissions' means or how it differentiates from sibling tools like forms_get_forms_submissions. This is a tautology with minimal helpful distinction.

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 guidance on when to use this tool versus alternatives. No prerequisites, typical scenarios, or exclusions are mentioned. The agent receives no help in deciding between this and similar submission-fetching tools.

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