erinys_export

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

No annotations are provided, so the description carries the full burden. It states the output format but does not disclose side effects, whether it is read-only, required permissions, or what happens to the exported data. The lack of behavioral details beyond the format is a gap.

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 sentence that is front-loaded with the verb and object. It is appropriately concise with no unnecessary words, earning its place.

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?

With an output schema present, return values need not be explained, but the tool has two optional parameters with no descriptions. The description does not provide enough context about parameter usage or when to apply this tool, making it incomplete for an agent to invoke correctly without guessing.

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 0% description coverage, and the description does not explain the 'format' or 'project' parameters. It only mentions 'markdown', which aligns with the default, but does not clarify other possible values or how 'project' filters observations. The description fails to compensate for the missing schema descriptions.

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 clearly states the tool's function: 'Export observations as markdown payload (Obsidian-compatible [[wikilinks]])'. It specifies the verb 'export', the object 'observations', and the output format, which distinguishes it from siblings like erinys_save or erinys_get.

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 for exporting observations in a portable format, but it does not explicitly state when to use it over alternatives or provide exclusions. The Obsidian mention hints at a use case but no direct comparison to sibling tools is given.

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