getLatestHouseDisclosures

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

Annotations already indicate readOnlyHint and idempotentHint, so description adds limited behavioral context. It mentions 'real-time' and 'recent trades' but does not disclose constraints like rate limits or data freshness beyond what annotations imply. Baseline 3 is appropriate.

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?

Two concise sentences, front-loaded with the main purpose. No wasted words; every sentence adds value.

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 simple parameters (2 optional), rich annotations, and no output schema, the description adequately covers the tool's function and data source. Could mention output format or pagination, but overall sufficient for a straightforward list endpoint.

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 fully describes both parameters (page, limit) with 100% coverage. Description does not add additional meaning for parameters, so baseline 3 is correct.

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?

Description clearly states the tool accesses real-time financial disclosures from U.S. House members, specifying the type of data (trades, asset ownership). However, 'access' is a generic verb; a more specific verb like 'retrieve' or 'list' would improve clarity. It distinguishes from siblings effectively by focusing on House disclosures.

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?

Description provides no guidance on when to use this tool versus alternatives like getHouseTrades or getSenateDisclosures. No explicit when-to-use, when-not-to-use, or references to sibling tools.

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