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

The description adds genuinely useful context about the shape of the result — roles, party affiliation, and quantified track-record metrics like bills sponsored and realization rate — which tells the agent this is more than a name lookup. It says nothing about permissions, rate limits, or result ordering, and it sits awkwardly against readOnlyHint=false: a "Search ... Returns" tool reads as non-mutating, so the annotation is at best confusing (the tool appears not to be a write operation). With annotations present the bar is lower, but this mismatch is worth surfacing rather than penalizing as a hard contradiction.

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 sentences with no filler, and the identifying information is front-loaded before the return-content detail. The second sentence partly restates what the output schema already declares, which is the only minor waste.

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?

The tool is simple (two optional parameters, output schema present), so the description needn't explain the return shape or pagination. What is missing is the routing information an agent needs to pick this over get_actor_profile, plus any note about result ordering or behavior when multiple people match a partial name.

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 description coverage is 100%, so both parameters are already documented, and the description merely echoes the query parameter's accepted forms (name, slug, congressional member ID). It omits the CIK input listed in the schema and says nothing about the limit parameter, so it adds no meaning beyond what the schema provides.

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?

States a specific verb and resource ("Search public figures") and enumerates the entity types it covers (corporate executives, politicians, regulators), so the agent knows exactly what is being looked up. However, it never differentiates itself from the obvious sibling get_actor_profile, which sounds like it retrieves the same kind of person-centric record; an agent with both tools available has no stated basis for choosing.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of alternatives, despite get_actor_profile and search_management_promises being close siblings. The only implied guidance is that it accepts an identifier (name, slug, congressional ID), which an agent would infer from the schema anyway.

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