list_habits

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

No annotations provided, so description carries full burden. It describes the return fields (habits with stats) and mentions auth requirement. Since it's a list operation, it implies read-only behavior, though read-only not explicitly stated. Adequate for a simple list.

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?

Description is concise with 4 meaningful lines: purpose, metadata, related tools, and return fields. No excess verbiage; well-structured.

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 no parameters and output schema present, description covers purpose and return fields. Does not mention pagination or ordering, but for a list with no inputs, it is fairly complete.

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?

Input schema is empty (0 parameters), so baseline is 4 per guidelines. Description adds return field details (id, name, status, etc.), adding value beyond 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?

Description clearly states 'List all habits with stats', specifying verb and resource. Distinguishes from sibling tools like list_habit_sections (lists sections) and get_habit_records (records for a specific habit).

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?

Lists related tools (create_habit, update_habit, habit_checkin, get_habit_records, list_habit_sections) providing context. Does not explicitly state when to use or exclude alternatives, but the category and related list offer implicit guidance.

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