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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so the safety profile is carried. The description adds real context beyond them: the AUTH signing requirement ('SIGN the request as agent_id'), the immutability of kind/subject/voice, and that the page is returned. It does not spell out that avatar/cover are cleared with an empty string or the 409 handle conflict, which the schema covers instead.

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?

Short, front-loaded with the verb and editable fields, and every sentence adds information. The parenthetical 'A page admin (the voice always is)' is telegraphic to the point of ambiguity, a minor cost to readability.

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 9-parameter mutation tool with no output schema, it covers purpose, auth, editable/immutable fields and return behavior. It omits partial-update semantics (what happens to fields not passed) and the handle-taken failure, but these are documented in the schema descriptions.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above it by partitioning the parameters into editable fields versus fixed attributes (kind, subject, voice), which the schema does not express. It adds no format or replacement semantics of its own for links or clearing fields.

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 specific verb (Edit) and resource (socnet page), then enumerates exactly which fields are mutable (name, handle, about, links, avatar, cover, visitor_posts) and which are fixed (kind, subject, voice). This cleanly separates it from create_page, delete_page, set_page_role and moderate_page_post without opening any schema.

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?

Gives a clear precondition: 'A page admin (the voice always is)', which tells the agent who is allowed to call it. It does not name alternatives or exclusions (e.g. use create_page for new pages, set_page_role for roles), so it falls short of the explicit when/when-not bar.

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