get_lords_interests_staff

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that this is a read/search operation returning matching records, but says nothing about pagination, result limits, ordering, or whether the search is exact vs fuzzy — meaningful gaps for a search tool with zero annotation coverage.

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 header repeats 'staff interests declared by Lords' in three pipe-separated fragments, and the Args/Returns sections restate the same fact. It is front-loaded and readable but has noticeable redundancy that could be trimmed.

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?

An output schema exists, so return-format detail is unnecessary (the description's Returns note is redundant but harmless). The single required parameter is documented with useful semantics, making the definition adequate for correct invocation.

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 0% (the schema only repeats 'Search Term'), so the description must compensate. It does so by clarifying that the term can match either staff names or interests, which is real added meaning beyond the bare schema.

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: searching staff interests declared by Lords. The resource is narrow enough to distinguish it from siblings like get_member_staff and get_lords_interests_register, though it does not name those alternatives explicitly.

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?

Provides a use case ('investigate potential conflicts of interest related to Lords' staff'), which implies when to reach for it. However, it gives no when-not guidance and does not distinguish it from adjacent interest-register tools, leaving the agent to infer the boundary.

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