surveys_get_surveys

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

The description adds no behavioral context beyond the annotations, which already declare readOnlyHint, destructiveHint=false, idempotentHint, and openWorldHint. While there is no contradiction, it also fails to mention any specifics like pagination, default location behavior (though locationId schema does), or what a survey object contains, offering no extra 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?

'Get Surveys' is extremely brief, but this is under-specification rather than effective conciseness. It sacrifices essential context for brevity, providing no structure or useful information that justifies its minimal length.

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 4 parameters (including undocumented ones) and no output schema, the description is grossly incomplete. It does not explain the meaning of 'type' or 'skip', nor does it describe the return format or any filtering behavior, leaving an agent under-informed for a 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 50% (only limit and locationId have descriptions), yet the tool description does not help with the undocumented parameters 'skip' and 'type'. It adds no meaning beyond the schema, failing to compensate for the uncovered parameters.

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' states a clear verb and resource, but it is nearly a tautology of the tool name and does not distinguish this from the sibling surveys_get_surveys_submissions. It communicates the basic action but offers no nuance about scope or filtering, so it is minimally clear but not informative.

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 absolutely no guidance on when to use this tool versus alternatives. No mention of the sibling surveys_get_surveys_submissions or any exclusion conditions, leaving the agent without direction on selection.

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