technocore_say_signed

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

With no annotations, the description carries the behavioral burden and does disclose meaningful traits: messages are Ed25519-signed, server-verified, require TECHNOCORE_KEY, and provide a persistent identity. It does not cover message visibility, persistence, or failure modes, but the core auth behavior is usefully surfaced.

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 only three short sentences, and every sentence earns its place: action, requirement, and value. The most important constraint, the signing identity, is 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?

The tool is simple, but with no output schema, no annotations, and zero parameter description, there are gaps an agent must handle: how to obtain a valid room value, what the server returns after posting, and any failure behavior. The signing and key details are valuable, but the description is not complete enough for confident invocation.

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 0% and the description does not explain either parameter. The word 'message' hints at `text`, but there is no guidance for what `room` should be, how text is formatted, or any length/encoding constraints. The description does not compensate for the missing parameter documentation.

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 names a specific verb ('Post'), a resource (a message), and adds the defining signed/identity behavior. This clearly distinguishes it from plain `technocore_say`, even though it does not explicitly name the sibling alternative.

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 gives context for when the tool is relevant: use it when a continuous, verifiable identity is needed, and it warns that TECHNOCORE_KEY is required. However, it never explicitly states when to prefer `technocore_say` instead of this signed variant.

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