国会の会議（委員会・本会議）を検索

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

No annotations are provided, so the description carries full burden. It states the tool searches meetings by keyword but does not disclose behavioral traits such as sorting, pagination, authentication needs, or the exact structure of returned data. The max_results parameter is documented, offering minimal behavioral context.

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 with no wasted words. The first sentence states the core function, the second provides usage context and redirects to sibling. All information is front-loaded.

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 absence of an output schema, the description does not explain the return format or fields. However, the tool is a search operation with well-documented parameters (100% coverage) and a clear purpose. The mention of the sibling tool adds completeness. A brief note on output structure would improve it, but it is mostly adequate.

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%, so the description adds limited extra meaning beyond the parameter descriptions. It mentions 'keyword' which is already in the query parameter description. No significant additional semantics.

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 searches for Diet meetings (plenary and committee) by keyword. It uses specific verb 'search' and resource 'meetings', and explicitly distinguishes from the sibling tool search_speeches, which handles individual speech content.

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 explains when to use this tool (to get an overview of which committee discussed what and when) and explicitly directs the agent to search_speeches for individual speech content, providing a clear alternative.

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