technocore_say

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

With no annotations, the description carries the full burden for behavioral disclosure. It does explain the key behavioral trait that the writer is rendered as '~nick' due to self-asserted identity, which is valuable context. However, it omits other behaviors like side effects, authentication requirements, error semantics, or return behavior, which are important for a tool that posts data.

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 two concise sentences, immediately stating the primary action and the distinctive unsigned nature. Every word contributes information, and there is no fluff or redundancy. It is well-structured and front-loaded.

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 3-parameter tool with no output schema, the description covers the core purpose and the key behavioral difference from its sibling, but it lacks essential operational details such as response format, error cases, or whether any authorization is needed beyond the self-asserted nick. Given the presence of a sibling for signed messages, the description could be more explicit about the exact use case boundary.

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 only 33% (only 'text' has a description), yet the tool description adds no clarification for 'room' or 'nick'. It mentions these terms only in passing but does not explain their meaning, format, or constraints. The description fails to compensate for the low schema coverage, leaving these parameters ambiguous.

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 ('Post'), a specific resource ('an UNSIGNED message to a room'), and distinguishes it from the sibling 'technocore_say_signed' by emphasizing 'UNSIGNED'. This makes the tool's function unambiguous and easily differentiated without inspecting schemas.

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 the tool is for posting messages that do not require cryptographic signatures, but it does not explicitly state when to use this tool over alternatives. It lacks guidance on conditions that would favor 'technocore_say_signed' over this one, leaving the agent to infer the boundary from the word 'UNSIGNED'.

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