get_vault_file_partial

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

No annotations provided, so description carries full burden. Describes what is returned (heading section exclusive of next same-or-higher). Does not address error behavior (e.g., heading not found, file missing) or edge cases like duplicate headings. Adequate for a simple read operation.

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?

Single sentence with parenthetical clarification. No wasted words, front-loaded with verb and object. Efficiently communicates the core behavior and boundary condition.

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?

Given 0% schema coverage and no output schema, the description should provide more context. It captures the essential functional behavior but lacks details on parameter values, error scenarios, and usage nuances. Adequate for a simple tool but incomplete for fully informed 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%, so description must add meaning. Only clarifies that targetType is 'heading', but does not explain what 'target' represents (e.g., heading text) or what 'path' is. Leaves two parameters partially or fully undocumented in terms of semantics beyond schema names.

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?

Description clearly states the verb 'Get' with specific resource 'content of a single heading's section from a vault file'. It precisely defines boundaries: includes heading line through next same-or-higher-level heading exclusive. This distinguishes it from siblings like get_vault_file (full file) and get_note_outline (structure only).

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?

Implies usage when a specific section under a heading is needed. Does not explicitly exclude alternatives or mention when not to use, but the focused description makes it clear this is for partial content. Lacks explicit when-not and alternative references.

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