get_onboarding_questions

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

No annotations provided. Description states it returns the questionnaire as markdown, but does not explicitly confirm non-mutability or side effects. Mention of 'instructions for saving memory and drafting plan' is ambiguous about whether the tool performs those actions.

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 paragraph with clear front-loading of purpose and trigger. The 'Returns:' line is helpful. Could be more structured (bullet points) for readability.

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?

For a zero-parameter, read-only tool with output schema, the description adequately covers purpose, trigger, and return type. No major 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?

No parameters in input schema. Baseline of 4 applies. Description does not need to add parameter meaning; it correctly focuses on the tool's outcome.

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?

Clearly states 'Load the onboarding questionnaire for a new athlete.' Specific verb+resource. Distinguishes from siblings like get_training_plan or read_coach_memory by focusing on the onboarding process.

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?

Explicitly says when to call: when read_coach_memory returns 'not been onboarded yet' or athlete section empty. Provides clear context but does not enumerate alternatives or when not to use.

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