me.learning_path

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

Adds beyond annotations: declares read-only, idempotent, auth requirements (Bearer token, any plan), and details return fields. No contradiction with annotations.

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?

Well-structured: purpose upfront, then WHEN TO/NOT TO, BEHAVIOR, Auth, Returns. No wasted sentences; each sentence is informative.

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?

Fully describes output fields, usage contexts, and auth. Without output schema, this is complete for an agent to understand and invoke the tool.

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 exist (coverage 100%), so schema is minimal. Description compensates by explaining the output in detail, though not directly about parameters. Baseline 4 is appropriate.

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 it returns the caller's Blueprint learning-path state with specific fields, using a specific verb 'returns' and resource. It distinguishes from siblings like me.coaching_context and me.validation_history.

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 provides WHEN TO CALL (user asks 'where am I', etc.) and WHEN NOT TO CALL (heartbeat, reading others' progress), directly helping the agent decide usage.

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