Get Page

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is handled. The description adds valuable context beyond those annotations by specifying the exact metadata fields returned and the default-Page fallback behavior. It does not cover error cases or pagination, but for a read-only single-object fetch this is sufficient context.

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 sentences deliver the purpose, the returned fields, and the parameter behavior with zero filler. The most important scoping detail ('one Page') is front-loaded, and the default behavior is presented compactly with a clear arrow implication.

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 one optional parameter, no output schema, and strong read-only annotations, the description covers the invocation essentials and the expected metadata fields. The only notable omissions are potential error/not-found behavior and a note about permissions, but these are minor for a simple read-only metadata fetch.

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 fully documents the single optional 'profile' parameter with 100% coverage, including the example value and the default behavior. The description essentially repeats what the schema already states, so it adds no new parameter semantics beyond the structured definition. Baseline 3 is appropriate because the schema carries the weight.

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 the specific verb 'Fetch metadata' and clearly identifies the resource as 'one Page,' distinguishing it from sibling list tools like facebook_list_pages by the singular scope. It also enumerates the exact fields returned, leaving no ambiguity about what the tool does.

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 clearly implies this tool is for retrieving metadata for a single Page rather than listing pages or retrieving posts/comments. It explains the optional profile key or Page ID and the default behavior when omitted, giving clear context for invocation. It does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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