list_business_activities

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, which cover the safety profile. The description adds no extra behavioral context beyond stating it fetches a list, so it does not conflict with annotations. Without annotations this would be insufficient, but here the structured data carries most of the transparency burden.

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, efficient sentence with no wasted words. It is appropriately front-loaded. However, it is slightly underwhelming in content, though conciseness itself is not compromised.

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 the complexity (3 optional params) and rich annotations/schema, the description is too thin to be fully complete. It does not explain what a business activity is, how to iterate over large result sets, or how this differs from `search_business_activities`. The openWorldHint is also unexplained, leaving the agent without critical context for a listing tool.

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 100%, so parameters (limit, offset, order_by) are well-documented in the schema. The description does not add any additional meaning or context about these parameters. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 that the tool fetches a list of business activities using a specific verb and resource. However, it does not differentiate from the sibling tool `search_business_activities`, which likely serves a similar listing purpose with filtering. The name helps, but the description alone could be more explicit about scope (e.g., 'all business activities').

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 `search_business_activities` or other list/search variants. There is no mention of alternatives, prerequisites, or typical use cases. The agent is left to infer usage from the tool name alone.

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