get_csat_survey_page

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that this is a read operation, whether it requires authentication, what it returns, or any side effects. The description is too minimal to inform an AI agent about the tool's behavior.

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 a single sentence and is concise in terms of word count, but it is under-specified. Conciseness should be balanced with informativeness; here, the brevity sacrifices clarity and completeness, making it less useful.

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?

There is no output schema, so the description should explain what the tool returns. It does not describe the return value, format, or any contextual behavior. Given the tool's simplicity (no parameters) and the presence of a sibling, the description is insufficient for an agent to understand its purpose and usage.

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 input schema has zero parameters with 100% coverage, so the schema already describes all parameters. The baseline is 4, but the description adds no extra semantics about the tool's operation or expected input. It is a bare statement that does not enhance understanding beyond the schema.

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 states 'Get CSAT survey page' with a clear verb and resource, but 'page' is ambiguous—it could refer to a single survey page or a page of results. It does not distinguish from the sibling tool 'list_csat_survey_responses', which likely lists responses, whereas this tool might fetch a single page object. The purpose is vague and lacks specificity.

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. The sibling 'list_csat_survey_responses' is closely related, but the description does not clarify the difference or suggest use cases. There is no context about prerequisites or when not to use it.

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