create-survey

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions session expiration, which is good, but does not cover authorization, rate limits, error handling, or the nature of the response. The disclosure is adequate but incomplete.

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 two sentences with no redundancy. Every sentence adds critical usage information, making it highly efficient and front-loaded.

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 complexity of a conversational survey builder, the description lacks details about the response format, error conditions, or what the agent returns. It covers basic usage and session management, but the agent would benefit from more context about expected outputs or limitations.

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 coverage is 0%, so the description must add meaning. It explains the session_id usage pattern (omit first, include later, expiration) which adds significant value beyond the schema. The 'message' parameter is not elaborated, but its purpose is self-evident from the tool context.

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 clearly states the tool sends a message to a survey-builder agent and enumerates its capabilities (create, edit, preview, publish, close, analyze). This makes the purpose explicit and distinct, despite no sibling tools provided.

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?

The description provides clear guidance on session handling: omit session_id on first call, pass the returned session_id on follow-ups, and notes session expiration after an hour. It lacks explicit when-not-to-use or alternatives, but the context is clear for a conversational agent.

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