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

Annotations indicate a write operation (readOnlyHint=false) that is not destructive. The description adds that it searches a 'real studio library' and logs the request, and every request gets read. This is transparent. However, it does not mention authentication requirements, rate limits, or error scenarios, which could be relevant for an agent.

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 two sentences long, front-loaded with the main purpose, and no redundant information. Every sentence adds value, making it easy for an agent to parse quickly.

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 the output schema exists (so return values are covered there) and annotations are present, the description is complete enough. It explains the end-to-end behavior (search, log, read) without omissions. The tool is simple (3 params, 1 required), and the description matches its complexity.

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?

Schema coverage is 100% with descriptions for all three parameters. The tool description adds value by emphasizing 'Provide both song title and artist for best results,' which goes beyond the schema's note. This extra guidance helps the agent choose better inputs.

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 action ('Submit a song request'), the specific resource ('KAZM 106.5 FM & 780 AM via the station website'), and the workflow (searches library, logs for DJ). It also provides a usage hint ('Provide both song title and artist for best results'). This distinguishes it from sibling tools like search_song_request_library, which is read-only.

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 implies usage for making a request that will be read by the DJ. While it does not explicitly mention when to avoid using it (e.g., if only searching), the context of sibling tools (mostly read-only get_* tools) and the action verb 'submit' make it reasonably clear. A brief 'Use this to send a request; use search_song_request_library to browse existing songs' would improve it.

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