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

With no annotations, the description must disclose behavior. It only says 'Company Page', revealing nothing about whether the tool performs a read operation, requires authentication, or returns specific data formats. This is a complete absence of behavioral information.

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?

Although only two words long, the description is under-specified rather than concise. It conveys no actionable information and reads as a placeholder label rather than a meaningful summary.

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 tool with no output schema and no annotations, the description is the sole information source. 'Company Page' leaves the agent completely uncertain about the returned data, error behavior, and relationship to sibling tools, making it inadequate for task completion.

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 input schema already fully documents the 'url' parameter with 'The URL of the LinkedIn company page to get', providing 100% schema coverage. The description adds no additional parameter context, so the baseline of 3 is appropriate.

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 is the fragment 'Company Page' with no verb or action. It only names the resource, making it a tautology of the tool name's subject. It does not specify that the tool scrapes or retrieves company page data.

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 is provided on when to use this tool versus alternatives like scrapecreators_company_ads or scrapecreators_search_for_companies. The description lacks any mention of use cases, prerequisites, or exclusions.

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