List Pages

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

Annotations only state readOnlyHint, but the description adds value by disclosing 'best-effort' behavior and the potential inclusion of followed non-admin companies. This goes beyond the annotation and helps the agent understand the reliability and scope of the results.

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 concise and front-loaded with the primary action and resource. It uses an em-dash to append essential caveats without redundancy. Every sentence/part earns its place, and it's easy to parse quickly.

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, parameter-free list tool with a read-only annotation, the description covers the essential aspects: what is listed, the scope, the best-effort nature, and a caution about posting. The lack of an output schema is not a gap because the description doesn't need to explain return values for this type of 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?

The tool has zero parameters, so the baseline is 4. The description adds meaning by defining the scope of the list ('surfaced to your account'), which effectively acts as a conceptual parameter even though there are no formal inputs.

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 the tool lists Company/showcase Pages surfaced to the account, using a specific verb ('List') and resource ('Pages'). It also distinguishes itself from sibling list tools by specifying 'Pages' and the 'surfaced to your account' scope.

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 clear context for when to use the tool: to see pages available to the account. It includes a caveat that results may include non-admin companies and advises verifying admin rights before posting. However, it does not explicitly name alternative tools or state when not to use this one, but the context is sufficient.

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