proofpage_business_profiles

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

No annotations are provided, so the description carries the full burden. "List" implies a read operation and "No network" suggests offline/local data, but nothing is stated about permissions, result size, ordering, or whether results are cached or may be stale — all material for a context-listing tool.

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?

Two short fragments, appropriately front-loaded, with no filler. However, brevity crosses into under-specification: "No network" is a dangling phrase whose meaning for the caller is unclear.

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?

With no output schema, no annotations, and no parameters, the description is the only source of behavioral detail — and it supplies almost none. An agent cannot tell what the returned profiles contain, how many there might be, or how this differs from its closest sibling.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description neither helps nor hurts here.

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?

States a verb and resource ("List local business context profiles"), so the basic operation is identifiable. But what a "business context profile" is remains undefined, and it is not distinguished from the sibling proofpage_business_context, which plausibly returns the same resource in singular form.

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?

There is no guidance on when to call this instead of proofpage_business_context or proofpage_get_context. The only extra hint, "No network," is not framed as a usage condition, so the agent must guess between sibling tools.

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