meta_get_page

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

There are no annotations to describe side effects or read-only behavior. The phrase 'details' weakly implies a read operation, but the description does not disclose response format, errors, authentication, or whether any state changes occur.

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 extremely short and free of irrelevant detail, making it easy to parse. It could be slightly more informative by adding a verb and scope, but it does not waste words.

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 getter, the description gives a general idea but omits critical context such as what details are returned, how fields affects output, and any prerequisites. An agent would need to infer too much from the tool name and schema.

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?

Only 'fields' has a minimal schema description ('Comma-separated. Defaults to id,name,fan_count.'), while 'page_id' has no description. The tool description adds no explanation of page_id or how the parameters interact, leaving an agent to guess from the parameter name.

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 indicates the resource is a Facebook Page's details, and the tool name includes 'get', so an agent can infer retrieval. However, it is a noun phrase without an explicit verb, and it does not clearly distinguish the scope from related tools like meta_create_page_post.

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 about when to use this tool versus alternative tools. Sibling names imply this is for reading Page details while others create posts/comments or fetch Instagram accounts, but the description itself does not state this.

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