billy_list_action_stream

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

The description includes 'READ-ONLY' which implies no side effects, but lacks additional behavioral details such as pagination behavior, data freshness, or any constraints beyond that. With no annotations provided, the description carries the full burden but falls short.

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 brief (two sentences) and front-loaded. However, it is too minimal to be fully informative. Every sentence earns its place, but more detail is needed.

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?

Given no output schema, no annotations, and only 2 parameters with 0% schema coverage, the description is insufficient. It does not explain pagination, what entries contain, or how to use the tool effectively.

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 description does not explain parameters (page, pageSize). The schema provides type and constraints, but the description adds no meaning to them, failing to compensate for the lack of parameter documentation.

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 clearly states 'Recent activity log entries', indicating the tool lists recent action logs. The verb 'list' is implied, and it distinguishes from other list tools by specifying 'action stream' in the name.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, filters, or exclusions, leaving the agent to infer usage context.

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