Fetch the full profile of a tradesperson by their UUID (or legacy WordPress integer ID). Includes bio, location, trade type, and bid statistics.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Tradesperson UUID or legacy integer ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It describes a read operation and lists included fields, but does not disclose any behavioral traits such as authentication requirements, rate limits, error handling, or whether the profile is cached. Basic description with no depth.
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, no wasted words. The most important information (what it does, what it returns) is front-loaded. Efficient and to the point.
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 fetch operation with one parameter and no output schema, the description adequately covers the purpose and return fields (bio, location, trade type, bid statistics). It could mention common errors or edge cases, but it is sufficient for basic use.
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% with one parameter 'id' described as a string. The description adds value by specifying that the ID can be a UUID or a legacy WordPress integer ID, which is not in the schema description. This clarifes acceptable input formats.
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 the verb 'Fetch' and the resource 'full profile of a tradesperson'. The description explicitly lists included fields (bio, location, trade type, bid statistics) and the identification methods (UUID or legacy integer ID). This distinguishes it from sibling tools like search_tradespeople which returns a list, and create_project which creates.
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?
Implied usage: when you have a tradesperson's UUID or legacy ID. However, no explicit guidance on when not to use it or alternatives. The sibling tools are different enough to infer use cases, but the description does not provide a direct comparison or context for selection.
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 targets a distinct action: project creation, profile retrieval, OTP request, tradesperson search, and conversation initiation. No two tools have overlapping purposes, ensuring clear agent selection.
Tools generally follow verb_noun pattern (e.g., create_project, search_tradespeople). Minor inconsistency: 'tradesperson_profile' uses singular while 'tradespeople' uses plural, but overall pattern is consistent and readable.
With 5 tools covering project creation, search, profiles, and chat, the set is well-scoped for a homeowner-tradesperson matching server. Each tool serves a clear role without redundancy.
Core workflow is covered (create project, search, start conversation), but notable gaps exist: no tools for updating/deleting projects, viewing bids, or managing conversations. Agents may face dead ends.
