Return ready-to-use share links (X/Twitter, LinkedIn) plus the canonical link and suggested text for a page on Gabriel S. Gusmao's site, so a user can share it in one click. Only pages on gabrielgusmao.com can be shared.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | https://www.gabrielgusmao.com/ |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses domain constraint but lacks details on return format, error handling, or side effects (though read-only assumed).
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, front-loaded with core function, second sentence adds critical constraint. No redundancy.
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 tool with one parameter and no output schema, description effectively explains outputs (share links, canonical link, text) and preconditions (domain restriction).
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?
Single 'url' parameter with 0% schema coverage; description clarifies it refers to a page on gabrielgusmao.com and links to actual parameter purpose, adding meaningful context.
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?
Clearly states it returns share links for social media platforms plus canonical link and suggested text, specifying the domain restriction. Distinct from siblings which cover bio, profiles, etc.
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?
Implies usage when wanting one-click sharing for pages on gabrielgusmao.com. No explicit exclusion of alternatives, but context is clear given sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: biography, expertise, profiles, share links, citation info, playgrounds, and publications. No overlap in functionality.
Most tools follow a verb_noun pattern (get_bio, get_expertise, list_playgrounds), though 'how_to_cite' is a phrase and deviates slightly. Overall consistent.
7 tools is appropriate for a personal information server covering key aspects of a single individual without being excessive.
Covers main areas: bio, expertise, profiles, publications, playgrounds, citation, sharing. Minor gap: no direct contact or CV tool, but core needs are met.
