get_survey_summaries

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get survey summaries' implies a read operation but doesn't specify whether it returns all summaries, filtered results, paginated data, or error conditions. It lacks details on permissions, rate limits, or response format, leaving significant behavioral gaps.

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 concise ('Get survey summaries') but borders on under-specification rather than efficient communication. It's front-loaded but lacks the necessary detail to be truly helpful. While not verbose, it fails to earn a higher score due to insufficient 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 no annotations, no output schema, and a vague description, the tool definition is incomplete for effective use. The agent lacks information on what the tool returns, how it behaves, or how it differs from siblings. For a tool with multiple related siblings, this minimal description leaves too many contextual gaps.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to compensate for any parameter gaps. While it doesn't add semantic value beyond the schema, the baseline for this scenario is 4, as the schema already provides complete parameter information.

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 survey summaries' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what 'survey summaries' are, what format they come in, or how this differs from the sibling 'get_survey_summary' tool. While it uses a clear verb ('Get'), it lacks the resource specificity needed for a higher score.

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 is provided on when to use this tool versus alternatives like 'get_survey_summary' or 'create_new_survey_summary'. The description doesn't mention context, prerequisites, or exclusions. The agent must infer usage from the tool name alone, which is insufficient for effective tool selection.

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