Debug Profile Controls

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only 'visible' controls on a 'profile page' — it does not explain what the after-click behavior does, whether it navigates or mutates the page, or any rate/session constraints for a debug probe.

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?

A single tight sentence with no filler and the resource front-loaded. It is not overly long, though its brevity comes at the cost of the missing detail noted elsewhere.

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?

An output schema exists, so return values need not be described. However, for a two-parameter diagnostic tool with zero schema documentation and a cryptic after_click_aria_label, the description leaves the agent without enough to call it correctly or know why it exists relative to its many siblings.

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 description coverage is 0% and the description explains neither parameter. The 'url' param could be inferred from 'profile page', but 'after_click_aria_label' is completely opaque — the description does not say it selects a control to click before dumping, which is exactly the kind of meaning this description needed to supply.

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 states a specific verb and resource: 'Dump visible button/link controls on a profile page.' That is enough to distinguish it from the action-oriented siblings (create_post, follow_person, get_person_profile), though it never explicitly frames itself as a debugging/diagnostic tool despite the name.

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 indication of when an agent should reach for this tool rather than get_person_profile, get_my_profile, or the other profile-related siblings, and no mention of what conditions make dumping controls useful. The presence of after_click_aria_label hints at an interaction flow, but that hint is never explained.

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