senado_videos_taquigrafia

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds the return structure and field names, but could mention any constraints like pagination. However, it does not contradict annotations and adds value by explaining the output format.

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 only two sentences: first states purpose and output, second provides usage guidance. It is front-loaded, efficient, and contains no wasteful information.

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 tool's simplicity, the description covers purpose, usage guidance, parameter semantics, and output schema. It is complete for an agent to correctly invoke the tool in conjunction with sibling tools.

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 description adds significant context beyond the schema descriptions: it tells the agent where to obtain the id and how to use the orador filter effectively. This goes beyond the brief schema descriptions.

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 tool lists videos and audio of a plenary session or committee meeting, specifying the output format and fields. It distinguishes itself from siblings by explicitly mentioning related tools for obtaining the session ID and for transcription.

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 explicitly tells when to use this tool (to get videos/audios), how to obtain the required id from other tools, and how to filter by orador or get transcripts via senado_notas_taquigraficas, providing clear guidance on tool usage.

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