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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only states the browsing/filtering intent. It does not disclose whether the operation is read-only, whether any side effects occur, what the return payload contains, whether pagination is handled beyond the limit parameter, or any authentication/rate-limit requirements. This is a significant transparency gap for a tool with zero annotation support.

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 front-loaded sentence that immediately conveys the resource and purpose, then lists the filtering and sorting dimensions without redundancy. Every clause earns its place, and no filler words are present.

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?

For a five-parameter tool with no output schema and no annotations, the description covers the core browsing and filtering semantics but omits important operational context: it never states what the returned testimonies look like, how results are paginated, or when to prefer this over the similarly named query_alerts sibling. It is minimally viable but not fully complete for an agent to invoke confidently.

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 coverage is 100%, so the baseline is 3. The description adds meaningful semantic mapping: 'perpetrator tool' clarifies target_tool, 'failure category' maps to failure_type, and 'recency or solidarity' explains sort_by. It also frames severity as a filter dimension. This extra interpretation helps the agent map real-world intent to the parameters beyond their raw schema names.

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 ('Browse'), a specific resource ('individual whistleblowing testimonies of conscience on the public grievance board'), and enumerates the filtering dimensions (perpetrator tool, failure category, severity) and sort options. This clearly distinguishes it from sibling browse tools in other domains (heritage, petition) and from injustice-specific actions like query_alerts or voice_conscience.

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 implies when to use the tool (to browse and filter testimonies) but provides no explicit when-not guidance or comparison to alternatives such as subctx_injustice_query_alerts. The action words 'Browse' and 'Filter' suggest a read-only listing use case, but there is no statement about when to choose this over sibling tools.

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