technocore_whoami

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

No annotations are provided, so the description must carry the burden. 'Report' implies a read-only operation, and it states what information is returned. However, it does not disclose whether there are any side effects, authentication requirements, rate limits, or the exact format of the returned data. For a simple query tool, the behavior is mostly transparent, but it could be more explicit that no state is changed.

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, front-loaded sentence with zero fluff. It states the core purpose immediately and includes the key output details without any filler. This is an exemplary model of conciseness.

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 zero-parameter, no-output-schema tool, the description fully covers what an agent needs to know: what it does and what it returns. The sibling tools are clearly unrelated in purpose, so there's no ambiguity. The description is complete given the tool's simplicity.

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 input schema has zero parameters, so there is nothing for the description to elaborate on. Per calibration, a baseline of 4 is appropriate when there are no parameters. The description correctly focuses on the output (did:key and publication location) rather than adding unnecessary parameter details.

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 ('Report') and a precise subject ('this agent's did:key and where its DID note is published'). It clearly distinguishes the tool from siblings like technocore_read_room and technocore_say, which deal with rooms and messaging, by focusing on agent identity metadata. The purpose is unambiguous.

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 implies usage: when you need to know the agent's identity or DID note location. However, it provides no explicit guidance on when NOT to use it or alternatives. The sibling tools are sufficiently different that an agent would likely pick this correctly, but the description leaves the 'when' to inference rather than stating it.

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