Get Recorder Info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds only 'settings and questions' but does not further disclose behavior (e.g., response size, performance). Given the existing annotations, the description provides minimal additional transparency.

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 a single concise sentence that front-loads the purpose. It efficiently conveys the tool's function without unnecessary words, though it could be slightly more structured (e.g., bullet points for settings and questions).

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 simple read-only tool with an output schema, the description is adequate. It explains what the tool returns (detailed info, settings, questions) and the context is clear given the sibling tools (many are write operations). The description covers the essential aspects without requiring further detail.

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 input schema has one parameter 'recorderId' with a description 'Unique identifier of the recorder.' Since schema description coverage is 100%, the description adds no extra meaning beyond the schema. The score is baseline 3.

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 uses a specific verb 'Get' and resource 'recorder', and clarifies the scope 'detailed information including its settings and questions.' This clearly distinguishes from sibling tools like 'list_recorders' or 'get_recorder_recordings'.

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 does not explicitly guide when to use this tool versus alternatives. While it is appropriate for retrieving detailed recorder info, no contrasts or exclusions are provided. The score reflects an adequate but unhelpful level of guidance.

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