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

The description adds meaningful context beyond the read-only annotations: share pages are public, usable without a Fetch Hive account, and any runs or messages are billed to the owning account. That billing consequence is important behavioral information not available in annotations or schema. It does not discuss pagination or status filtering, but the annotations already establish the safe read-only profile.

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 front-loaded with the core concept and stays short. The final fragment, 'Optionally for one workflow or one agent,' is slightly unclear and could be integrated more cleanly, but overall it is efficient.

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 simple list tool with annotations and mostly documented parameters, the description covers the resource and the public/billing implications well. However, it leaves the status filter and the returned listing shape unexplained, which is a noticeable gap for an agent trying to use the tool without an output schema.

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 description broadly covers the workflow_id and agent_id filters by saying the list can optionally be for one workflow or one agent, but the schema already documents those parameters. It adds no explanation for the status filter and does not clarify limit behavior beyond what the schema provides.

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 identifies the resource as the workspace's share pages and explains that they are public links for running workflows or chatting with agents. It does not explicitly name or distinguish itself from siblings such as get_share or update_share, which keeps it below a 5.

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?

Usage is implied: list share pages, optionally narrowed to one workflow or one agent. There is no explicit when-to-use guidance, no mention of when to use get_share instead, and no exclusions.

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