get_recent_placements

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it doesn't confirm this is a read-only operation, note pagination or result capping via limit, mention auth/session requirements, or describe ordering. "Recent" is the only behavioral signal, and it is defined only implicitly by the days parameter.

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?

It is a single compact sentence with no filler, which is good front-loading. However, the brevity stems from under-specification rather than disciplined editing; a list tool with two undocumented parameters needs at least one more clause.

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 values needn't be described. Still, for a tool with zero annotation coverage and 0% parameter documentation, the description is thin: defaults, result ordering, and pagination behavior are all missing despite being relevant to calling it correctly.

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%, so the description must explain the two parameters. "The last X days" loosely maps to days, but the default (30) is unexplained and the limit parameter (default 100) is never mentioned, leaving half the inputs undocumented in both places.

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 states a specific verb and resource ("Get recent Bullhorn placements") plus a scope constraint ("from the last X days"), so an agent knows exactly what it retrieves. It doesn't distinguish itself from siblings, though no other sibling appears to cover placements, so differentiation is largely moot.

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 guidance on when to choose this over alternatives such as query_entities, search_entities, get_activity, or get_recruiting_metrics, nor any note that the X-day window defaults to 30. The agent must infer usage entirely from the name.

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