survey_agent_skill

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. The description mentions 'auth, endpoints, group-bound token' but does not explain what operations are performed, whether data is mutated, what permissions are needed, or any side effects. This is almost entirely opaque.

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 (5 words), but it is not concise in a helpful way. It omits essential information, making it under-specified rather than efficient. Every word should earn its place, but here the words are vague and uninformative.

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 one parameter, an output schema, and many siblings, the description is far from complete. It does not explain the tool's purpose, its input/output behavior, or how it relates to other survey agent tools. The presence of an output schema reduces the need to document return values, but the description still fails to provide basic context.

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 schema has 100% coverage (one parameter), but the description adds no meaning to the 'format' parameter. The parameter's purpose, allowed values, and effect are not described. With 0% schema description coverage, the description fails to compensate.

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 'Agent skill: auth, endpoints, group-bound token' is cryptic and does not clearly state what the tool does. It fails to identify any verb or resource, and it does not distinguish the tool from its many siblings like survey_agent_get or survey_agent_update. The name suggests it relates to survey agent skills, but the description offers no actionable purpose.

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. With over 30 sibling tools, the description offers no context for selection, no prerequisites, and no exclusions.

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