mbs_press_releases

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does disclose that results are 'mostly direct PDF links under /mbs/wp-content/uploads/', which is a useful detail, but it omits other behaviors like whether ordering or pagination is applied, what fields are returned, or potential errors. This is only a minimal behavioral disclosure.

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 a single sentence, front-loaded with the verb and resource, and the parenthetical adds relevant detail without redundancy. Every word earns its place, making it highly concise and well-structured.

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 (one optional parameter, no output schema), and the description gives the core purpose and the nature of the links, which provides a basic sense of what the response contains. However, it lacks guidance on selecting this tool among siblings and does not describe return format or additional behaviors, so it is only minimally complete.

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?

The schema description covers 100% of the single parameter 'limit' with 'Max items (default 20)'. The tool description does not mention or elaborate on this parameter, so it adds no value beyond the schema. Baseline 3 is appropriate.

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 uses 'List press releases' as a specific verb+resource, clearly stating the tool's action and object. The parenthetical 'mostly direct PDF links under /mbs/wp-content/uploads/' adds distinguishing detail that separates it from sibling tools like mbs_publications or mbs_census_releases.

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 provides no guidance on when to use this tool versus alternatives such as mbs_census_releases or mbs_publications. There is no mention of context, exclusions, or alternative tools, leaving the agent to infer usage solely from the tool name.

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