list_deeptutor_capabilities

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description's 'informational' note reinforces this but does not add substantive behavioral context beyond what annotations provide. The 'unless' clause is more about usage than tool behavior. No contradiction; minimal additional value.

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 entire description is a single, efficient sentence. It front-loads the core action ('List installed DeepTutor capabilities') and appends the usage qualifier. Every word earns its place with no filler or redundancy.

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?

The tool has no parameters, has an output schema to describe return values, and annotations cover its safety profile. The description provides the essential purpose and a usage caveat, leaving no critical information missing for correct invocation. It is fully adequate for an agent to use this tool appropriately.

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?

The tool has zero parameters, and the schema is empty with 100% coverage. Baseline for 0 params is 4. The description correctly avoids parameter details since there are none, so nothing is missing. No additional semantics needed.

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 the verb and resource: 'List installed DeepTutor capabilities'. This is specific and distinct from other tools that deal with DeepTutor sessions or status, though it doesn't explicitly name a sibling. It conveys the primary purpose without ambiguity.

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?

The description adds a usage nuance: 'informational unless the user directly requests a DeepTutor conversation'. This implies when to use it (informational requests) and hints it shouldn't be used for starting conversations, but it does not explicitly mention alternative tools or provide clear when-not-to-use scenarios. Guidance is implied rather than explicit.

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