moltbook_profile

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely says 'Get profile' and does not mention whether authentication is required for 'self', what happens for nonexistent names, or the response structure. This falls short of transparent behavioral context.

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 a single, short, front-loaded sentence that directly states the purpose and the one relevant condition. No wasted words or redundant information.

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?

The tool is simple with one optional parameter and no output schema, but the description still leaves gaps: it does not explain what 'self' means in terms of authentication, nor does it indicate error cases or return format. It is minimally sufficient but not fully complete.

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?

The schema has one optional string parameter 'name' with 0% description coverage. However, the description's phrase 'self or name' effectively explains that providing a name fetches that profile, while omitting it fetches the self profile. This compensates well for the schema's lack of detail.

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 'Get profile for self or name' clearly states the action (get), the resource (profile), and the two modes (self or specified name). It is specific and understandable, but does not explicitly distinguish it from the sibling tool 'moltbook_me', which may also target the current user.

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?

The description provides no guidance on when to use this tool versus alternatives like 'moltbook_me' or 'moltbook_profile_update'. There are no exclusions or context indications, so an agent has limited information to select it over very similar sibling tools.

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