ask_question

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

No annotations provided; description adds language detection behavior but lacks disclosure of whether tool is read-only, destructive, or any side effects. No mention of permissions, rate limits, or return 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?

Single sentence of 14 words, front-loaded with purpose, no filler. Every part is meaningful.

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?

Covers main action and language detail but does not describe return value (e.g., answer, error handling) or how language detection works. With no output schema, more explanation would be helpful.

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?

Description adds value beyond 100% schema coverage by explaining language detection ('Detect user language') and providing examples. Schema describes language parameter but description contextualizes its use.

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?

Specifies verb 'Ask' and resource 'question for the active session'. Clearly distinguishes from sibling tools 'start_session' (initiation) and 'give_up_and_reveal' (different action). However, no explicit differentiation statement.

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?

Implies usage after starting a session, but no explicit when-to-use or when-not-to-use guidelines. Does not mention alternatives or prerequisites.

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