get_page

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

With no annotations, the description carries the full burden. It indicates a read-style operation and names returned fields, but it does not disclose permission requirements, error behavior, or whether the linked Instagram account lookup requires extra scopes.

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?

One short, front-loaded sentence with no filler. The action, resource, and key data points are all included without repeating the input schema.

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 a single required parameter, no nested objects, and an output schema that already covers return shape, the description is nearly sufficient. It lacks only explicit alternative-routing guidance, but an agent can use it correctly.

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 schema has 0% description coverage, and the description does not explain page_id format or meaning. However, the single parameter is self-naming, and the description clarifies that the Page being detailed is identified by this ID, providing minimal compensation.

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 uses a specific verb ('Détaille') and resource ('une Page Facebook') and lists concrete fields — abonnés, description, compte Instagram lié — which distinguish it clearly from sibling tools like get_page_insights or get_page_audience.

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: call it when you need the main profile details of a specific Facebook Page. There is no explicit when-to-use guidance and no mention of alternatives such as get_page_insights or list_pages.

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