subscriptions-and-session-keys

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

No annotations exist, so the description must disclose behavioral traits. It notes this is a lesson (implying read-only), but fails to mention whether it requires authentication, what happens on invocation (e.g., displays text), or side effects. The safe, read-only nature is not explicitly stated.

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 very concise (two sentences) and front-loads 'Lesson 15'. However, it is arguably under-specified; conciseness does not compensate for missing critical details.

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 output schema and no annotations, the description is insufficient. It does not explain return format, prerequisites, or how this lesson relates to others. A more complete description would clarify the expected behavior and content.

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?

There are no parameters, so the baseline is 4 per the rules. The description adds no param information, but that is acceptable since none exist.

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 identifies it as "Lesson 15 of the curriculum" and mentions ERC-7715 scoped autonomy, implying an educational resource. However, it lacks a clear verb indicating what the tool does (e.g., read, learn) and does not distinguish it from other lesson tools like 'start-here'.

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?

No explicit guidance on when to use this tool versus alternatives. The phrase 'When to ask, when to refuse, scope-discipline rules' describes the lesson content rather than usage context. Sibling tools are all educational, so differentiation is missing.

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