profile

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The single word 'profile' reveals nothing about whether this is a read or write operation, what data it accesses, authentication requirements, rate limits, or any other behavioral characteristics.

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?

While technically concise with a single word, this represents severe under-specification rather than effective brevity. The description fails to convey necessary information, making it ineffective despite its minimal length. Every word should earn its place, but this word provides almost no value.

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 tool with no annotations, no output schema, and 80+ sibling tools, the description is completely inadequate. It provides no information about what the tool returns, how it behaves, or how it differs from related tools. The context demands much more comprehensive documentation.

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 tool has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate given the empty schema. This meets the baseline expectation for parameterless tools.

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?

Tautological: description restates name/title.

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 offers absolutely no guidance on when to use this tool versus alternatives. With no context about purpose or behavior, there is no basis for understanding appropriate usage scenarios or distinguishing it from other tools like 'info', 'self', or 'detail'.

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